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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description adds that deletion is effective only after re-sync ('Re-sync to re-project without it') and that read-only API keys cannot use this tool, which is useful behavioral context beyond the annotations. No contradiction.

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, front-loaded with the action and resource, followed by the re-sync implication and API key restriction. Every sentence carries meaning and no fluff is present.

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 tool with full schema coverage and annotations, the description covers the key steps: obtaining the id and the post-delete re-sync requirement. It omits explicit permanence warning, but destructiveHint covers that, and there is no output schema to explain. Slightly more could be said about model_id requirements, but the schema handles it.

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 100%, so the baseline is 3. The description only references mapping_id via 'from layerz_list_mappings', which the schema already states explicitly. No additional parameter semantics are added beyond the schema.

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?

States the specific action ('Delete'), the resource ('import classification rule'), and the source of the identifier ('from layerz_list_mappings'), distinguishing it from sibling tools like layerz_set_mapping and layerz_list_mappings. The verb and object are 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?

Gives clear context that the rule id comes from layerz_list_mappings and that a re-sync is needed after deletion. It does not explicitly name alternative tools for creating/modifying rules, but the delete-vs-edit distinction is evident from the tool name and sibling set.

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