Delete Group

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

The description clearly states the action is permanent and cannot be undone, which aligns with the destructiveHint annotation. It adds context about the effect on associated markups. However, it does not mention the idempotentHint (it is idempotent as a DELETE), which is a minor 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 concise and front-loads the key purpose. There is minor repetition of 'permanently delete' and 'cannot be undone', but overall it is efficient and includes useful API endpoint details.

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 the tool has no output schema, the description does not mention return values or expected outcomes beyond deletion. The optional parameter 'delete_resources' is not explained, leaving some uncertainty for the agent. It covers the main use case but lacks detail on response format.

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 coverage is 100%, so the description adds no extra meaning beyond what is already in the schema. It only reiterates the required parameters and API endpoint. The optional 'delete_resources' parameter is not explained further.

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 indicates the tool is for deleting a group related to Document Markup records. It specifies that markups in the group will need to be moved or deleted, which adds clarity. However, it could better differentiate from the similar sibling tool 'delete_a_single_group'.

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?

The description states to use this for permanently deleting Document Markup records and lists required parameters, but does not provide explicit guidance on when not to use it or suggest alternatives. The contextual impact on markups is noted, but no exclusions or comparisons to other delete tools are given.

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