get_callback_payload

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

No annotations are provided, so the description carries the burden. It discloses the return content (headers, decrypted body, metadata) but does not mention side effects, auth requirements, or rate limits. For a simple fetch operation, this is adequate but not highly transparent.

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: first sentence states the action and what is returned, second sentence provides usage guidance. No extraneous words, front-loaded with key information. Every sentence earns its place.

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 with one parameter. The description explains what the tool returns (headers, decrypted body, metadata) and provides workflow context (after wait_for_callback or list_callbacks). No output schema, but description covers the return well. Complete for this complexity.

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?

The schema already describes requestId with detailed context ('Callback UUID, from wait_for_callback or list_callbacks'). Schema coverage is 100%, so baseline is 3. The description does not add additional meaning beyond the schema, so score remains 3.

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 verb 'Fetch' and the resource 'a single received callback with full headers, decrypted body, and metadata', which precisely defines the tool's purpose. It also distinguishes it from siblings by mentioning the use case after wait_for_callback or list_callbacks.

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?

The description explicitly says to use this tool after obtaining a callback ID from wait_for_callback or list_callbacks, providing clear usage context. It doesn't explicitly state when not to use it, but the workflow implication is sufficient. Sibling tools have different purposes, aiding differentiation.

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