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

Beyond the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false), the description adds valuable behavioral context: the return format ('Returns a branded SVG that renders directly in the chat') and the focus-highlighting mechanism. Generating an in-chat artifact with no side effects is consistent with the readOnly/idempotent annotations, so there is no contradiction.

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?

Three dense sentences that each earn their place: core purpose, chart-type options, then output behavior and the focus feature. The chart-type enumeration is long but necessary for correct invocation, 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 tool with no output schema, the description compensates by stating precisely what is returned (a branded SVG that renders in chat). The per-chart data shapes in the schema plus the chart-type semantics in the description cover all call paths, though error conditions and data-size limits are not addressed — a minor gap for a 2-parameter generation tool.

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 coverage is 100%, so the baseline is 3, but the description genuinely elevates it by decoding each chart_type enum value ('implication_ladder' = Signal→Trend→So What→Do What, 'opportunity_map' = 2×2 white space analysis), which helps an agent select the correct variant. It also front-loads the focus parameter behavior that the schema buries inside a JSON-string description.

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+resource pair ('Create a presentation-ready data visualization from research findings') and then enumerates six concrete chart types with their conceptual shapes (e.g., 'cultural_shifts' = From→To transitions). This unambiguously distinguishes it from the sibling tools, which are all get/search/list/read operations, so an agent can tell this is the generation tool without opening the schema.

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 purpose statement implies the clear usage context — when a visual artifact is needed rather than raw data — and the chart-type list guides which configuration to pick. However, the description never explicitly states when to prefer this over alternatives or what conditions rule it out, so it stops short of full exclusion guidance.

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