Live Chart

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that the chart auto-refreshes and no user action is needed, clarifying the polling behavior. No contradictions, and it adds useful behavioral context beyond 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 three sentences, each serving a purpose: stating functionality, usage guidance, and behavioral note. No redundant information; it is front-loaded and efficient.

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?

Given the tool's complexity (14 parameters, 3 required) and the rich schema descriptions, the description adds enough context for an AI agent to use the tool correctly. It does not explain error handling or output, but the tool renders a chart rather than returning data, so that omission is acceptable.

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 100%, so the baseline is 3. The description provides extra context, such as suggesting 'poll_http' as the typical pollTool and that pollArgs can contain a preset or URL, adding meaning beyond the schema's parameter descriptions.

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 renders a real-time auto-updating line chart that polls a tool. The verb 'render' and resource 'live chart' are specific, and the inclusion of 'polls a tool' distinguishes it from static chart siblings like render_bar_chart.

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 explicitly advises 'Use when the user wants to MONITOR a live data source' and provides guidance on setting pollTool to 'poll_http'. While it lacks explicit when-not-to-use or alternative tool names, the guidance is clear and actionable.

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