Delete Rounding Configuration

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

Annotations already provide destructiveHint=true, and the description adds strong emphasis that deletion 'cannot be undone' and 'permanently removes' records, which reinforces the destructive nature. It also provides the API endpoint and module, adding context beyond annotations. No contradictions.

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 contains redundant phrases: 'permanently delete' and 'Permanently removes' are similar, and 'This cannot be undone' is repeated. While the first sentence is clear and front-loaded, the repetition wastes space and reduces conciseness. It could be shortened without losing information.

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 simple delete endpoint with one parameter, the description covers the basic context (API module, endpoint, required parameter) but does not explain what happens if the company_id is invalid or if the rounding configuration does not exist. There is no output schema, so return values are not mentioned. It is adequate but not thorough.

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 one parameter (company_id) described in the schema. The description only mentions that it is required, which is already in the schema. It does not add any additional meaning or format details, so the value is baseline.

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 verb 'Delete' and the resource 'rounding configuration', and specifies it targets 'Field Productivity records'. It distinguishes from sibling tools like 'create_rounding_configuration' and 'update_rounding_configuration' by explicitly being the delete operation. The purpose is specific and unambiguous.

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 tells when to use the tool (to permanently delete rounding configurations) but lacks guidance on when not to use it or alternatives (e.g., using update to modify instead of delete). It also does not mention prerequisites like required permissions. The instruction is clear but incomplete.

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