modify_plot

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

No annotations provided; description mentions mutation and output but does not disclose side effects (e.g., overwriting original), error handling, or reversibility. Incomplete disclosure for a mutation tool.

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?

One concise sentence effectively communicates action and output. Could potentially include that all parameters are optional except plot_id, but not necessary given schema. Well structured and 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?

Description is too brief given tool complexity (9 parameters) and absence of annotations. Fails to mention that plot must exist, that changes are applied in-place, or constraints like immutability. Output mention is helpful but insufficient.

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 covers all parameters with descriptions (100% coverage). Description adds minimal value beyond schema, simply grouping parameters under 'appearance.' Baseline of 3 is appropriate.

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?

Description clearly states action ('Modify an existing plot's appearance') and output ('Returns updated PNG + HTML'). Distinct from siblings that create, clone, describe, or export plots.

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?

Implies use when modifying an existing plot's appearance, but no explicit when-to-use or alternatives guidance. Lacks context for when to choose this over annotate_plot or other related tools.

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