Delete field group

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

The description merely repeats the 'Destructive' flag already present in annotations (destructiveHint=true), adding no additional behavioral context such as irreversibility, cascading effects, or permission requirements. With openWorldHint=true, more explanation would be valuable.

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 concise at two short sentences, with no filler or redundant text beyond the necessary warning. It is easy to parse.

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 delete operation with no output schema, the description offers only a terse warning. It does not explain what happens to associated data, whether the action is reversible, or how the required entity_type and id should be selected, leaving critical context absent.

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%, and the description does not mention parameters. While the schema defines id and entity_type with an enum, the description fails to compensate for the lack of explanation about their meaning or relationship.

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 states the action 'Delete' and the resource 'field group', which precisely distinguishes it from sibling field group tools (list, get, create, update). It is unambiguous and specific.

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 provides no guidance on when to use this tool versus alternatives. It only warns 'Destructive' but does not explain prerequisites or scenarios for deletion.

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