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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description goes beyond annotations by specifying the response contents (bio, images, taxonomies, stats, related performers), which sets expectations. No contradictions.

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 sentence with a clear verb and resource, front-loaded and concise. Every word adds value; 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 one-parameter read tool with strong annotations and an output schema, the description covers purpose, id semantics, and response content. It could mention when not to use it, but given the simplicity and context from siblings, it is nearly complete.

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?

Only one parameter 'id' exists. The schema defines it as number with an example, and the description adds that it is the 'numeric id' for a performer. This is minimal but sufficient for a single, self-explanatory parameter. Schema coverage is 0% but the description provides contextual meaning.

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 uses a specific verb 'Fetch' with resource 'full SeatGeek performer profile' and method 'by numeric id', listing contents (bio, images, taxonomies, stats, related performers). This clearly distinguishes it from sibling tools like performer_by_slug (which uses slug) and performers (which lists).

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 phrase 'by numeric id' implies the tool is appropriate when you have a numeric performer identifier, contrasting with performer_by_slug. However, it does not explicitly name alternatives or provide exclusion criteria, so some inference is needed.

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