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

While annotations handle safety (ReadOnly, Non-destructive), the description adds the crucial behavioral constraint that the download link is only valid for 'five minutes.' This temporal limitation adds significant, non-obvious context.

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 definition is extremely concise, delivering the core action and the required access level in only two short, functional sentences with zero wasted words.

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 being concise, the description is incomplete for a tool involving a restricted, time-sensitive link. The zero% schema description coverage requires the description to clarify input fields, which it fails to do, leaving critical information missing for the AI agent.

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, but it only provides a generic statement about the goal. It fails entirely to give semantic meaning to the required 'offer_id' or optional 'request_id'.

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?

It provides a clear prerequisite constraint ('Requires creator or admin access'), which serves as a usage guideline. However, it does not specify the ideal timing or conditions for when this tool should be used versus other related offer management tools.

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