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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds important behavior: the person is emailed on every result and the agent should never loop when waiting. These are valuable operational constraints beyond the structured annotations.

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 front-loaded with the read action and remains compact, with each sentence carrying operational content. It is slightly dense but does not waste space on restating the title or annotations.

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 tool with two required undocumented parameters and no output schema, the description leaves critical gaps: request_id and request_capability are unexplained and the return shape is only partially implied. The behavioral guidance is helpful, but the definition is not complete enough for reliable invocation without external knowledge.

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 both parameters are required, yet the description says nothing about what request_id or request_capability mean, where to obtain them, or how they affect the call. With no schema compensation, an agent lacks essential invocation details.

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 read operation and lists the main data returned: current request, questions, sample, and next action. It does not differentiate from siblings such as get_order, get_payment_status, or get_quote, so an agent cannot fully tell which retrieval tool to choose without more context.

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?

It gives some conditional guidance, such as how to handle accepted payment reminders and what to do when next_action is wait with suggested_check_after_seconds. However, it never says explicitly when to use this tool instead of related siblings like get_order or get_payment_status.

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