Get a chart's props + example

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

No annotations exist, so the description carries the full burden. It describes the returned data (import paths, props, etc.) but does not disclose whether the tool is read-only, requires authentication, or has side effects. It is not misleading but lacks full transparency.

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, which is concise. It front-loads the main purpose but lists many items in a run-on manner; could be broken into shorter sentences for clarity. Nevertheless, it efficiently conveys the scope.

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 simple parameter, an output schema (defining return structure), and two sibling tools, the description is complete. It covers what is returned, how to use the output with 'render_microchart', and provides all necessary context for an agent to invoke it correctly.

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% with one parameter 'slug'. The description adds value by providing an example value ('sparkline') and clarifying it's the chart identifier, which goes beyond the schema's minimal 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 clearly states it retrieves full wiring detail for a single chart by slug, listing specific components like import paths, props, data shape, and example. It also distinguishes from sibling 'render_microchart' by mentioning that the sample can be passed to it, and 'find_microchart' is implicitly different.

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 when you need detailed chart wiring, but does not explicitly state when to use this vs. 'find_microchart' (which likely searches) or 'render_microchart' (which renders). No when-not or exclusion criteria are provided.

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