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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is covered; the description goes further by disclosing the blast radius precisely – it changes no record and no past run, only configuration a future run would read, and can disable a tool until reauthoring. It omits whether the deletion is reversible or any auth requirements.

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?

Three tight sentences, front-loaded with the action, then the prerequisite, then the scope of effect. Every sentence earns its place; no filler.

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 no output schema, the definition covers the action, a prerequisite, and the consequences well. It could add reversibility or auth context, but nothing essential for correct invocation is missing.

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% and both parameters already carry descriptions that state the list-first workflow, so the schema does the heavy lifting. The description reinforces the list_rule_templates prerequisite but adds no new meaning about template_id or connection_id 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?

Names a specific verb ("Remove") and resource ("a rule configuration"), and the name plus description clearly identify the rule-template target, distinguishing it from sibling deletes like delete_run. It does not explicitly contrast with update_rule_template or delete_run, but the resource is 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?

Explicitly prescribes a prerequisite workflow: "read what exists with list_rule_templates before removing one," and warns about the consequence of deleting the only template of a needed kind. No explicit when-not conditions, but the guidance is clear and actionable.

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