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

Annotations only declare readOnly=false, openWorld=true, idempotent=false, destructive=false. The description adds useful behavioral context beyond those: 30-day hosting, public access without sign-in, expiry refresh on repeated share creation, and a warning not to include private information. These are meaningful traits an agent could not infer from the 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?

The description is front-loaded with the core purpose, then adds hosting behavior, repeat-call semantics, an exclusion, payload selection, and a security guardrail. Every sentence contributes distinct, useful information without redundant filler.

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?

The description covers trigger, payload selection, storage duration, access model, repeated-call behavior, and privacy caution — enough to invoke the tool correctly. The only notable gap is that it does not explicitly describe the return value (the link itself), and with no output schema the agent must infer that from the name and context.

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?

Top-level schema description coverage is 0%, so the prose must compensate. The description adds the key disambiguation: kind 'score' pairs with score, kind 'play' pairs with pattern. It does not enumerate nested fields, but those are already richly described inside the schema, so the description covers the essential selection logic.

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 opens with a specific verb and resource: 'Create a hosted music share link'. It immediately scopes the tool to 'only when the user asks to share or store a piece online', and it distinguishes itself from playback tools by stating 'Playback does not require this tool'.

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?

It gives an explicit trigger condition (share or store online), an explicit exclusion (playback does not require this tool), and a precise payload-selection rule: 'Provide kind "score" with score, or kind "play" with pattern'. This is strong routing guidance with no ambiguity.

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