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

Goes well beyond annotations by disclosing that the action cannot be undone (reinforcing destructiveHint), changes take effect on the next scheduled processing cycle, existing scores/matches are not retroactively updated, and a free Prowlo account is required. This provides essential behavioral context beyond the structured metadata.

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 is moderately long but every sentence serves a purpose: deprecation notice, functional scope, alternative tool reference, irreversibility, scheduling, side effects, and auth requirement. It is front-loaded with the most critical info and contains 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?

Given the confusion risk with watcher_delete and the deprecation, the description covers all necessary operational aspects: what it acts on, what it does, when it takes effect, what is not updated, account requirement, and the replacement tool. No output schema is needed for a delete operation, and the description is sufficient for correct use.

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 schema already fully describes the single 'id' parameter with 100% coverage, including its provenance from tag_rule_list. The description adds context about what the rule is but does not enrich parameter semantics beyond the schema. Baseline 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?

The description clearly states 'Remove a TAGGING RULE' and disambiguates from Keyword Monitor entries by referencing watcher_delete. It also provides the rename target tag_rule_delete, making the tool's purpose and relationship to siblings 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 says when to use this tool (to stop a tagging rule from tagging posts) and when not to (Keyword Monitor entries, which are watchers), naming the alternative tool watcher_delete. Also notes the deprecation and rename, providing clear guidance on tool selection.

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