delete-chart

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

With no annotations, the description carries full behavioral disclosure burden. It only says 'Delete a chart', but fails to mention the two boolean parameters (hardDelete, recursive) that significantly alter behavior (soft vs permanent delete, child deletion). The agent cannot infer these traits from the description alone.

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 with no wasted words, but it sacrifices important information for brevity. It is front-loaded with the core action, but structure could be improved to include parameter behavior.

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 3 parameters (id, hardDelete, recursive) and no output schema or annotations, the description is too sparse. It does not mention the existence of optional parameters, their effects, or the default behavior (soft delete, non-recursive). An agent lacks critical context to use the tool 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 description coverage is 100%, so the schema already documents all parameters. The description adds no extra meaning beyond 'Delete a chart by UUID'. Baseline is 3 due to high coverage, but it does not enhance understanding of parameter defaults or interactions.

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 'Delete a chart by UUID', specifying the action (delete), the resource (chart), and the identifier method (UUID). Among siblings with many delete-* tools, this distinguishes the specific entity being deleted.

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?

No guidance is provided on when to use this tool versus other delete tools (e.g., delete-data-product) or when not to use it. There are no comparisons, prerequisites, or context about alternative methods, leaving the agent without decision support.

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