RetrieveResult

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

No annotations are provided, so the description carries the full burden of disclosing behavior. The vague '(re)retrieve' hint at a possibly idempotent operation, but it does not explain side effects, required permissions, rate limits, or what response the caller should expect. This is inadequate behavioral disclosure.

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?

Though the description is short, it is under-specified rather than economically complete. The single sentence contains no actionable information beyond a restatement of the name, so it does not earn its place in any meaningful way.

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?

With no output schema and no annotations, the description must define the object being retrieved and the typical workflow context. It does neither, and the large sibling list further emphasies that an agent has no way to understand why or when RetrieveResult would be called.

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 tool has zero parameters and the schema coverage is 100%, so there is nothing for the description to add about parameter meaning. Per the calibration baseline for zero-parameter tools, this is as good as needed.

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 '(Re)retrieve Response Result.' essentially restates the tool name 'RetrieveResult' and does not define what a 'Response Result' is or where it comes from. It is tautological and fails to distinguish this tool from any of the many sibling tools such as StatusCheck or notifyResult.

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?

There is no guidance about when to use this tool or when to prefer an alternative. The description neither states a use case nor mentions any conditions that should lead the agent to invoke it instead of a sibling.

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