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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered; the description adds useful context that results include exclusions and a direct intake URL, which tells the agent the output is decision-ready. It stops short of noting catalog volatility (e.g., whether the 17 offers change), which would have pushed it higher.

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?

Three short sentences, each carrying distinct information: selection trigger, return payload, and follow-on sequencing. Nothing is repeated from the title or annotations.

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 parameters and no output schema, the description fully compensates by listing the fields returned and by placing itself in a three-step workflow (qualify_task → list_offers → get_acceptance_tests). An agent has everything needed to call it correctly on the first attempt.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for 0 params applies. The description adds no call syntax because none is 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?

States the resource ('full 17-option catalog') and enumerates exactly what each offer carries (price, delivery window, required inputs, exclusions, intake URL), so an agent knows the tool's output shape without opening it. It is clearly distinguished from qualify_task, which is scoped to a single need.

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?

Explicit when-to-use ('comparing the full catalog'), explicit alternative with its trigger ('for a single sanitized need, start with qualify_task'), and a sequencing rule ('use get_acceptance_tests only after selecting an offer'). This is a full routing decision, not an implication.

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