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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the 'without downloading it' efficiency guarantee and the 'Free' cost signal — neither of which appears in structured fields. It stops short of describing rate limits or response shape, but the added cost/bandwidth context is genuinely useful.

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 short sentences, zero filler, with the operation and its returned fields front-loaded before the cost qualifier. Every clause earns its place.

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?

For a read-only metadata tool with rich annotations and a fully documented single parameter, the description is nearly sufficient, and it usefully enumerates the returned fields in lieu of an output schema. Minor gaps remain around ticket sourcing and error behavior, but nothing critical for correct invocation is missing.

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?

There is a single 'ticket' parameter with 100% schema description coverage ('Any ticket for the item.'), so the schema already carries the semantics. The description adds nothing about ticket format or sourcing, which is the expected baseline when the schema does the heavy lifting.

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 states a specific verb ('Check') and resource ('an item') and enumerates the metadata returned — size, fingerprint, label, expiry — so the agent knows exactly what this tool yields. It doesn't explicitly contrast itself with siblings like anthill_retrieve or anthill_store, but the 'without downloading it' phrasing implicitly separates it from retrieval.

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?

Usage is implied rather than stated: 'without downloading it' signals this is the cheap metadata-only path versus anthill_retrieve, but no sibling is named and no explicit when/when-not condition is given. An agent can infer the intent but must do the routing work itself.

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