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

No annotations are available, so the description carries the full burden. 'Delete' implies destructive action, but it does not disclose whether deletion is permanent, what happens to associated metric versions, or if any confirmation is required. This is a significant transparency 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 incredibly short and front-loaded, but it is under-specified. It is not verbose, yet it omits key details about the id parameter and behavioral implications, making it less useful than a slightly longer, more informative description.

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?

For a simple delete tool with one parameter, the description covers the basic action, but given the absence of annotations and output schema, more context is needed. It does not mention side effects, what the id represents, or how to verify success, leaving the tool under-specified for reliable invocation.

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?

The schema has one parameter (id) with 0% schema_description_coverage, and the description does not mention the id parameter at all. It fails to explain what the id refers to (e.g., the metric group's unique identifier), leaving the agent to infer from the schema alone.

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 'Delete a metric group' uses a specific verb and resource, clearly indicating the action. It distinguishes from siblings like metric_groups_create/update/get, though it could be confused with metrics_delete if not parsed carefully.

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 usage guidance is provided. There is no mention of when to use this tool versus alternatives, no preconditions, and no exclusions. The description gives no context for decision-making.

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