Delete Project Insurance

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

The description aligns with annotations (destructiveHint: true, idempotentHint: true) and adds context about the permanence and irreversibility of the deletion. It also lists required parameters. The 'Directory records' mention slightly undermines clarity but does not contradict annotations.

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 relatively concise but contains redundancy: both 'Delete the specified Insurance' and 'Permanently removes the specified Directory records.' The API endpoint details are included, which may be useful for troubleshooting but are not essential for tool selection. Slightly repetitive.

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 annotations and full schema coverage, the description adequately covers the action's irreversibility and required parameters. There is no output schema, so return value details are not expected. The description provides sufficient context for an agent to understand the tool's basic behavior and prerequisites.

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 input schema has 100% coverage with descriptions for each parameter. The description highlights the required parameters, which adds minimal value beyond the schema's 'required' array. No additional semantic context is provided beyond what the schema already offers.

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 'Delete the specified Insurance' and mentions 'permanently delete', making the primary purpose obvious. However, it also refers to 'Directory records', which could cause confusion since the tool is specifically for insurance. Overall, the intent is clear and distinguishes from other delete tools by specifying the resource type.

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 guidance on when to use this tool (to permanently delete insurance records) and states the required parameters. It notes that the action cannot be undone, which sets expectations. However, it does not explicitly mention when not to use it or compare it to alternative tools for similar actions among the extensive sibling list.

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