Delete Keyword Group

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

No annotations are present, so the description must carry the burden. 'Delete' implies mutation and potential destruction, but the description does not disclose whether the operation is irreversible, if it requires specific permissions, or if it affects related data like keywords within the group.

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 very short, but includes the redundant phrase 'Project Tool:' which is unnecessary given the title and tool name. The sentence is otherwise clear but could be more concise.

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 destructive operation with no output schema and no annotations, the description should at least mention irreversibility or success criteria. The current description is minimal and does not provide enough context for an agent to understand the full implications.

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 100% coverage for the group_id parameter, so the description adds no new information about the parameter. The mention of 'Requires a project ID' is not relevant to the actual parameter and could be misleading.

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 'Delete a project keyword group' which is clear about the action and resource. However, it also says 'Requires a project ID,' which is misleading because the schema only requires a group_id, not a project ID. This reduces clarity.

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 sibling tools like PROJECT_deleteCompetitor or PROJECT_moveKeywordsToGroup. There is no mention of prerequisites or alternatives.

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