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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile needs no restating. The description adds genuine context by characterizing the output as hard limits on what Zinvyl may claim, but it says nothing about format, size, or stability beyond that. Useful but not rich 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?

Two sentences, zero filler, and the sequencing instruction is front-loaded before the return-value description. Every clause carries information an agent needs.

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, the description does the work of telling the agent the nature of the returned data (acceptance tests, exclusions, evidence boundaries), which is enough to know why to call it. It lacks any indication of return shape or volume, a minor gap for a single-parameter read lookup.

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 100% and the single parameter is a fully enumerated offer ID with its own description listing valid values. The description adds no syntax, format, or fallback detail beyond what the schema already provides, so the baseline of 3 applies.

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 uses a specific verb-plus-resource framing: it returns 'the exact delivery acceptance tests, exclusions, and evidence boundaries' for a given offer. That is clearly more than a restatement of the name. It does not, however, distinguish itself from a similarly scoped sibling such as get_purchase_requirements, which an agent might confuse with it.

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?

'Use after list_offers or qualify_task identifies an offer' gives an explicit prerequisite and names the two upstream tools that feed it. There is no when-not guidance or statement of what this call enables downstream, so it stops short of full routing guidance.

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