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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety expectations. The description adds context that the data comes from the 'Ticketmaster Discovery API' and details the exact structure returned (segment, genre, sub-genre hierarchy), which goes beyond what annotations provide.

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, well-structured sentence that front-loads the core purpose and then specifies the returned data hierarchy. No unnecessary words or redundancy, making it appropriately concise.

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 get-by-ID tool with a rich output schema, the description is mostly complete: it names the resource, the lookup method, and the expected data hierarchy. The only gap is the undocumented 'locale' parameter, but given the output schema covers return values, this is a minor omission.

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 0%, and the description only hints at the 'id' parameter via 'by ID'. The optional 'locale' parameter is completely undocumented, leaving it unexplained. Since the schema provides no descriptions, the description should compensate but only partially addresses the parameters.

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 it returns 'full detail for a single classification by ID', specifying both the resource (classification) and the scope (single by ID). It distinguishes itself from the sibling tool 'classifications' (plural) which likely handles listing or searching, making the purpose unambiguous.

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 the tool is used when you have a specific classification ID and want detailed hierarchical data. However, it does not explicitly mention when to use this over alternatives like 'classifications' or provide any exclusion criteria, leaving usage guidance implicit.

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