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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds useful context beyond that — the tool returns the complete (not excerpted) and canonical (authoritative) version of lyrics, scoped to a single historical song. No contradictions exist between the description and annotations, but richer behavioral detail (failure modes, formatting) is absent.

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?

Two sentences totaling roughly 35 words, with the highest-value information ('START HERE', 'complete canonical lyrics') front-loaded. Every clause earns its place. It loses a point only for the slightly run-on, punctuation-stripped second sentence that crams three imperatives together awkwardly.

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 read-only, single-parameter tool with strong annotations and no output schema, the description covers the essentials: what is returned (complete canonical lyrics), the scope (one historical song), and how to begin (start here, try discipline, prepare an interpretation before publication). The undocumented enum values and unspecified return format are minor gaps given the tool's simplicity and the annotations carrying the safety profile.

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 single 'song' parameter has 0% schema description coverage, so the description partly compensates by defining the parameter's scope ('one historical song') and offering a concrete working example ('Try song=discipline'). However, it does not explain the 22 enum values or how to disambiguate between them — the example covers only one value, leaving most of the enum self-documenting.

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 states a specific verb ('read') and resource ('complete canonical lyrics for one historical song'), which clearly distinguishes it from siblings like search_corpus (searching) and campfire_catalog (cataloging). The title reinforces the same contract: 'Read a complete published song.' An agent can tell exactly what this tool does and what it returns.

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?

'START HERE' explicitly positions the tool as the workflow entry point, and 'before considering any authorized publication' gives ordering guidance relative to downstream steps. This is clear contextual usage direction, though it stops short of naming alternatives or exclusion conditions ('when not to use this, use X instead'), so it doesn't earn a 5.

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