chart_component

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

No annotations are provided, so the description carries the full burden. It doesn't disclose whether this is a pure transformation (no side effects), whether it validates the spec first, what happens with invalid specs, or whether it returns code as a string vs. a component. The description is too thin to convey behavioral traits.

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, concise sentence that front-loads the action and output. It earns its place, though it could add a bit more context without becoming verbose.

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 has one nested object parameter with 0% schema coverage, no annotations, and an output schema, the description is too sparse. It doesn't explain what a valid spec looks like, what the output schema contains, or how this relates to the sibling tools. An agent would need to inspect the output schema and guess at the spec format.

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%, and the description only mentions 'chart spec' without explaining the spec structure, required fields, or format. The schema itself is a generic object with additionalProperties: true, so the description adds minimal meaning beyond the parameter name. It doesn't compensate for the lack of schema documentation.

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 states a specific verb ('Return') and resource ('equivalent shadcn/Recharts JSX for a chart spec'), which clearly distinguishes it from siblings like render_chart and validate_spec. It could be slightly more explicit about the transformation nature, but the core purpose is clear.

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 this tool is for converting a chart spec into JSX code, which is distinct from rendering or validating. However, it doesn't explicitly state when to use this over render_chart or validate_spec, nor does it mention any prerequisites or context.

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