mgmt_chart_annotation_delete

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does state the destructive nature ('Delete'), but it does not mention whether deletion is irreversible, whether management access or permissions are required, what happens if the annotation is in use, or what response to expect. For a mutation tool, this is a significant gap.

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 short and front-loads the operation, but the leading URL is a noisy, incomplete reference and the text is essentially a restatement of the tool name. It is appropriately brief for a simple action, yet it sacrifices useful context.

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?

The tool is simple and all parameters are documented, but there is no output schema and no annotations, and the description gives no information about response behavior, errors, authorization, or side effects. An agent may know how to invoke it from the schema but lacks sufficient context for correct and safe 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 description coverage is 100%, so all three parameters are already documented in the schema (counterId, id, pretty). The description does not add extra meaning beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb and resource: 'Delete chart annotation'. This is clear enough to distinguish the tool from sibling delete tools (e.g., mgmt_filter_delete, mgmt_goal_delete) because the target resource is explicit. However, it does not explain what a chart annotation is or add any clarification beyond the tool name.

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?

There is no guidance about when to use this tool versus alternatives, no prerequisites, and no discussion of which ID is required or how deletion interacts with related resources. The only implicit usage signal is the verb 'Delete', which is not enough for a management operation.

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