renderChart

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns 'SVG string or validation errors' and lists available components, which adds some behavioral context. However, it lacks critical details: whether this is a read-only operation, if it has side effects, performance characteristics, authentication needs, or rate limits. For a tool with no annotations, this is insufficient.

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 appropriately sized with two sentences: one stating the purpose and return values, another listing components. It's front-loaded with the core functionality. However, the component list is lengthy and could be summarized more efficiently (e.g., 'Available components include LineChart, BarChart, and 20+ others').

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 no annotations, no output schema, and a tool with 2 parameters (including a complex nested object 'props'), the description is incomplete. It doesn't explain the structure of 'props', provide example inputs, describe error handling, or detail the SVG output format. For a visualization tool with nested parameters, this leaves significant gaps for an AI agent.

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 adds minimal value beyond the schema: it lists specific component examples (e.g., 'AreaChart', 'BarChart') which slightly clarifies the 'component' parameter, but doesn't explain 'props' object structure or provide usage examples. It doesn't compensate for any gaps since coverage is already high.

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 the tool's purpose: 'Render a Semiotic chart to static SVG' with specific verb ('Render') and resource ('Semiotic chart'). It distinguishes from siblings by specifying chart rendering rather than configuration diagnosis, schema retrieval, issue reporting, or chart suggestion. However, it doesn't explicitly differentiate from 'suggestChart' which might be related.

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 usage context by listing available components, suggesting this tool is for chart visualization. However, it provides no explicit guidance on when to use this tool versus alternatives like 'suggestChart' or other siblings. No prerequisites, exclusions, or comparative context are mentioned.

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