waha_get_session

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden; it discloses the returned fields, which suggests a read operation but never states it is non-mutating or that it fails for unknown sessions. The existence of an output schema lowers the need to describe return values in detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence, front-loaded with the verb and result. It is efficient, though it leaves no room for the missing parameter and error context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with an output schema, the basics are covered, but the unspecified 'session' parameter and the absence of any error or not-found behavior leave meaningful gaps given there are no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the sole required parameter 'session' is undefined — the description never says whether it is a session name, ID, or default. Nothing in the description compensates for the undocumented parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get one session') and names the returned content (status, linked WhatsApp account). The singular 'one' implicitly contrasts with waha_list_sessions, though that sibling is never named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the singular lookup phrasing; there is no explicit guidance on when to prefer this over waha_list_sessions or waha_status, and no mention of behavior when the session identifier does not exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.