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

Annotations already establish read-only, non-destructive, closed-world behavior. The description adds useful context about response content—current version, decisions, and delivery states—but does not cover error behavior, authorization needs, or missing-id handling.

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?

The description is a single tight sentence with no wasted words, and the core action is front-loaded. It is appropriately sized for a simple by-id read tool.

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?

The tool is simple, and annotations cover its safety profile, but with no output schema the description should more fully explain return values or not-found behavior. It lists returned content at a high level but remains thin on parameter semantics and error conditions.

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?

There is only one parameter, id, with 0% schema description coverage. The description does not mention the id parameter at all, so it fails to compensate for the missing schema description, even though the schema provides UUID type and pattern constraints.

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?

The description states a specific verb and resource: 'Read one approval request,' and enumerates what is returned (current version, decisions, delivery states). It clearly implies retrieval of a single approval by id, distinguishing it from list tools, though it does not explicitly name a sibling alternative.

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 implied by 'Read one approval request,' suggesting this tool is for fetching a single approval by id. However, it gives no explicit when-to-use guidance, prerequisites, or comparison to alternatives such as get_decision or list_approvals.

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