delete_chart

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

No annotations provided. The description discloses key behavioral detail: 'The data is unaffected.' However, it does not mention permissions, reversibility, or error conditions, leaving gaps.

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?

Two concise sentences with no unnecessary words. Front-loaded with the core action and immediate reference to list_charts.

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?

Basic delete tool with no output schema. Description covers the main action and data safety, but lacks parameter explanations and return information, adequate but incomplete.

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%. The description does not explain any of the three parameters (session_id, chart_index, sheet), leaving the agent to infer solely from names and schema.

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?

Clearly states verb 'delete', resource 'chart by index', and references sibling 'list_charts' for obtaining the index, effectively distinguishing from other tools.

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 usage by referencing list_charts, but lacks explicit when-to-use or when-not-to-use guidance, and doesn't mention alternatives or prerequisites beyond the index.

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