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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds field-level detail (address, city, etc.) but does not add behavioral context beyond what annotations provide, such as pagination, rate limits, or response-specific caveats.

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 description is a single, front-loaded sentence with no fluff. It efficiently states purpose, scope, and key response fields, earning every word.

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 simple one-parameter tool with a rich output schema and safety annotations, the description is mostly complete. It lacks explicit mention that 'venues' is the plural/list alternative, but the singular focus is clear. Overall sufficient for an agent to invoke it correctly.

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 coverage is 0% for the 'id' parameter, and the description only says 'numeric id', which is redundant with the schema's type: number and example. It does not explain what the id represents (e.g., SeatGeek venue id), nor does it add meaningful semantics beyond the schema.

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 clearly states the verb (Fetch), resource (full SeatGeek venue record), and method (by numeric id). It distinguishes from the sibling tool 'venues' by specifying a single-record lookup with full detail.

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?

The description implies use for retrieving a venue by its numeric id, but does not explicitly state when to use this tool over alternatives like 'venues' or contrast with list operations. No exclusions or alternative tool mentions are provided, so usage guidance is only implicit.

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