describe_plot

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

The description discloses that the tool runs a code-generation loop using an AI agent (Gemini, opencode), which is a key behavioral trait. It mentions slower performance but does not cover data privacy or timeout risks. With no annotations, this is fairly transparent.

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, front-loading the main purpose, then adding context about speed and return format. No redundant information.

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, the description covers the input (data and description), the process (code generation), the output (JSON same as siblings), and comparisons to related tools. It is complete for agent use.

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 baseline is 3. The description adds meaning by explaining data as 'rows as JSON objects' and description as 'natural-language description', going beyond the schema's minimal wording.

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 builds a Plotly figure from data and a natural-language description, and returns JSON. It distinguishes from siblings by naming quick_plot and create_figure and noting it is slower.

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 says to use this for open-ended chart requests and that it is slower than other tools, guiding when to use or avoid it. It names alternative tools for similar tasks.

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