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

With no annotations, the description carries the full burden. It discloses that the item is public, costs $0.01 USDC, sends 80% to the curator, and includes specific content (ordered tracks, artist/title, links). It does not mention error behavior or auth requirements, but provides substantial operational detail.

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 two sentences long and front-loaded with the core function. Every clause adds meaningful information—identifier format, output contents, pricing, and payout—without any redundancy or fluff.

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 tool with one parameter and no output schema, the description is remarkably complete. It covers input format, return content, cost, and payment distribution. There is no significant missing context needed for an agent to select and 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?

The schema only says tape_id is a string, but the description fully explains valid forms: a tape uuid or top10-<handle>, and what the latter means. This is critical contextual information the schema lacks, and it compensates perfectly for the 0% schema description coverage.

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 ('get') and resource ('One public SFtunes item by tape_id'), clearly indicating it retrieves a single item. It distinguishes itself from sibling tools like list_tapes by emphasizing 'One' and by specifying the identifier format.

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 retrieving a single item when you know the tape_id, and contrasts with list_tapes for browsing. It does not explicitly state when not to use it or name alternatives, but the context is clear enough for an AI agent to choose appropriately.

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