contentrain_content_delete

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

Adds value beyond annotations by disclosing auto-commit to git and the behavior of omitting keys for dictionary deletion. No contradiction with annotations (destructiveHint: true).

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 sentences, front-loaded with purpose, followed by key usage detail and warning. No unnecessary words.

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?

Adequately explains deletion behavior and git integration, but lacks clarification on when to use 'id' vs 'slug' (collection vs document) and does not mention the required 'confirm' parameter. No output schema, so return behavior is unspecified.

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%, so baseline is 3. The description adds context for 'keys' usage, but does not elaborate on other parameters like 'id' vs 'slug' or 'confirm' beyond 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?

Description states 'Delete content entries' and differentiates between dictionary and collection deletion, clearly indicating the tool's purpose. Siblings include contentrain_content_list and contentrain_content_save, so this is distinct.

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?

Provides guidance on using 'keys' for dictionaries and warns against manual editing after use, but does not explicitly compare to sibling delete tools like contentrain_model_delete or specify when not to use this tool.

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