check_request

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

With no annotations, the description discloses 'Non-blocking' behavior and authorization requirements. It does not detail return format or errors, but output schema may cover return values.

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?

Two sentences with no wasted words: first states purpose and blocking nature, second adds critical permission constraint. Front-loaded and efficient.

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?

Given output schema exists, the description covers purpose, blocking, and authorization. Missing error handling details, but for a simple poll tool this is largely sufficient.

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 coverage is 0%, but the description implies request_id identifies the info-request. It adds context but does not explicitly describe parameter format or source, leaving some gaps.

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 clearly states the tool checks if an info-request has been answered, using a specific verb and resource. It distinguishes from sibling tools like request_info and respond_info by focusing on polling status.

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 explains that only the creating session may poll, preventing enumeration attacks. This provides clear context but lacks explicit when-to-use or alternatives, though siblings imply the workflow.

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