mapping_delete

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

Discloses irreversibility and impact on imports (historical records kept, new imports cannot use it). With no annotations provided, this adequately covers key behavioral traits, though more detail on permissions or error conditions could improve it.

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?

Two concise sentences: first states action, second explains consequence. No filler or redundancy; highly efficient.

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 simple delete operation with two required parameters and no output schema, the description covers purpose, irreversibility, and effect on imports adequately. Missing details on success response, but not critical for tool invocation.

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% with clear descriptions referencing other tools. The description does not add extra meaning beyond the schema, so baseline score of 3 is appropriate.

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?

Clearly states verb and resource: 'Deletes a saved mapping.' This distinguishes it from mapping_create and mapping_update, and the additional sentence about irreversible nature and import behavior clarifies the scope.

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?

Implied usage (when you want to delete a mapping) but no explicit when-to-use versus alternatives (e.g., mapping_update to disable). No prerequisites or exclusions mentioned.

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