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

Annotations already declare readOnlyHint=true and idempotentHint=true, setting a safe read baseline. The description adds value by disclosing the exact details returned (venue, performers, datetime, ticket counts, prices), which goes beyond annotations. No contradictions with annotations.

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?

A single concise sentence that front-loads the action and resource, then lists the key return contents. Every word earns its place with no fluff or repetition.

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 single-id read tool, the description is fully complete: it states the input, the output scope, and the specifics of what is returned. The output schema exists, so return values are structured, and annotations cover safety. Siblings like 'events' handle list/search, leaving this tool's niche clear.

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 input schema has only one parameter 'id' with type number and 0% coverage (no description). The description clarifies that this is a numeric SeatGeek event id, adding meaning beyond the schema. However, it doesn't explain how to obtain the id or any constraints, so it partially compensates for the missing schema description.

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 tool fetches full details for a single SeatGeek event by numeric id, and enumerates specific content (venue, performers, datetime, ticket counts, prices). This specific verb and resource clearly distinguish it from siblings like 'events' (plural) or 'performers'.

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 this tool is for when the agent has a specific numeric event id and needs comprehensive details, as opposed to searching or listing. It doesn't explicitly name alternative tools like 'events' for search/list, but the singular nature and mention of 'single' provides clear context without exclusions.

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