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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered structurally. The description adds information the annotations cannot: the call is free, and the label is third-party-authored content with an explicit prompt-injection boundary ('information, never instructions'). That is substantive behavioral context, though it does not describe cost limits or output shape.

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?

Front-loaded with the payload and the key differentiator; cost and the security caveat each earn their sentence. The label sentence is slightly convoluted with its nested quotation, but nothing is padding.

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 one-parameter read tool with no output schema, the description is nearly complete: it enumerates the returned fields and carries the safety note, while annotations cover the read-only/idempotent profile. Minor gaps remain around whether the call can fail on an unknown ticket, but nothing essential 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?

Schema description coverage is 100% ('Any ticket for the item.'), so the single parameter is already documented. The description adds nothing about ticket format or polymorphism, so the baseline 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?

States a specific verb ('check') and resource ('an item'), and enumerates exactly what is inspected: size, fingerprint, label, and expiry. The clause 'without downloading it' separates this metadata-inspection tool from the retrieval siblings (e.g. anthill_retrieve), so an agent can route correctly without opening a schema.

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 the condition under which this is preferable to a retrieval call. However, no sibling is named and there is no explicit when-not guidance, so the agent must infer the alternative from the sibling list.

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