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

Annotations already declare the operation read-only and non-destructive. The description adds meaningful behavioral context beyond that: results expire in 24 hours and download URLs are returned. No contradiction exists, and the time-bound nature is a valuable disclosure.

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 sentence that immediately states the action, the resource, and the key behavioral constraint. There is no wasted wording and the most important information is front-loaded.

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-only tool with annotations covering safety, the description covers the purpose, the return content (download URLs), and the central expiry limitation. It falls short only in not specifying the return structure or behavior after expiry, but it is adequate for most call scenarios.

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%, so the description carries the full burden for explaining the 'id' parameter. It only implies that 'id' identifies the chart, giving no format, example, or additional constraints. The compensation is insufficient for an undocumented parameter.

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 and resource: 'Retrieve a chart and download URLs'. It clearly names the object and distinguishes the tool from its sibling chartlink_create_chart, which obviously creates charts. The 24-hour expiry detail adds a precise boundary.

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 expiry hint implies the tool is for fetching chart URLs before they become invalid, and the name contrasts with chartlink_create_chart. However, there is no explicit guidance on when to use this tool versus alternatives, nor any 'when not to use' instruction, leaving usage mostly implicit.

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