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

The annotations are extremely rich, detailing read-only, idempotent, and non-destructive nature. The description itself merely restates the purpose and adds no unique behavioral context (like specific API limitations, latency, or error handling) beyond what the structured annotations already provide.

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 maximally concise, using a single sentence that perfectly encapsulates the tool's function without any wasted words or unnecessary fluff.

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?

Despite having strong annotations for safety, the definition is functionally incomplete. The complete lack of parameter semantics, especially given the 0% schema coverage, means the agent cannot reliably construct the required input payload.

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%, meaning the description must explain the parameters. It fails to provide any meaning or context for either 'offer_id' or the optional 'request_id', making it nearly impossible for an agent to use the optional parameter correctly.

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?

Tautological: description restates name/title.

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 provides no guidance on when to use this tool versus other offer-related endpoints (e.g., a general 'read' endpoint). It simply states what the tool does, leaving the agent to infer the necessary use case.

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