groups_reports_delete_one

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

No annotations are present, so the description carries full responsibility. It only indicates an HTTP DELETE but fails to disclose that the operation is destructive, irreversible, or any side effects. Basic behavioral information is missing.

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 extremely short but not effectively concise. It wastes two lines restating the name and an HTTP path that adds little value. It lacks essential information, making it insufficient rather than efficient.

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?

Despite the simplicity of the tool (one parameter, no output schema), the description fails to provide complete context. It does not state the return value, error behavior, or confirm that the report is permanently deleted.

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 sole parameter item_id is only defined in the schema with type and format. The description does not explain what item_id represents or how to obtain it, leaving the agent without crucial context.

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 One' repeats the tool name without clarifying the resource (group report). It does not distinguish from sibling tools like groups_reports_get_one or groups_reports_get_all. A clearer description would specify 'Delete a single group report by its ID.'

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 alternatives. There is no mention of prerequisites, context, or exclusions. Siblings like groups_reports_get_one and groups_reports_get_all exist but the description gives no advice on tool selection.

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