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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds no meaningful behavioral context beyond stating the action, such as what constitutes a signed decision receipt, what happens on failure, or any side effects. 'Free' is irrelevant to behavior.

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 extremely short and has no fluff, but the prefixed 'Free:' is a distraction and the overall structure is an under-specified single clause. While concise, it lacks essential detail, making it more of a fragment than a well-structured explanation.

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 operates on a 'signed decision receipt' without any context about what that is, how to obtain one, or what verification entails. With no output schema and a single nested object parameter, the description is far too minimal to be contextually complete, especially alongside numerous sibling verification tools.

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 the description provides no information about the structure or required fields of the 'receipt' object. The schema only specifies type 'object' with no properties, leaving the agent without any semantic guidance on what to pass. The description fails to compensate for this gap.

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's action ('verify') and specific target ('a signed decision receipt'), which is a unique resource among the sibling verification tools. It distinguishes itself from siblings like verify_company_status or verify_passport by focusing on decision receipts.

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?

No guidance is provided on when to use this tool versus alternatives. The description simply states what it does without mentioning use cases, prerequisites, or exclusions. Given the large number of sibling verify_* tools, the absence of contextual usage guidance is a notable gap.

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