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

Beyond the readOnlyHint and idempotentHint annotations, the description adds substantial behavior: deprecation status and removal date, that it returns term/status/match statistics, that changes apply on the next scheduled cycle, that scores/matches are not retroactively updated, and that it requires a free Prowlo account (with a signup link). This is far richer than the annotations alone.

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 front-loaded with the critical deprecation notice and rename, then flows logically through purpose, distinction, return values, effect timing, retroactivity, and account requirement. Every sentence adds necessary information, with no fluff or repetition.

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 tool has no parameters, no output schema, and is a simple list operation, the description covers everything: what it lists, how it differs from sibling tools, what it returns, when changes apply, what is not retroactively updated, and the account prerequisite. It is fully self-contained for an agent to select and invoke correctly.

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 tool has zero parameters and the schema coverage is 100% (empty properties), so there is nothing for the description to add. The baseline of 4 applies for a no-parameter tool, and the description correctly focuses on behavior rather than parameter syntax.

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 is highly specific: it states the tool lists your org's TAGGING RULES, immediately clarifies it is the renamed version of tag_rule_list, and explicitly distinguishes it from keyword_monitor_list. This fully disambiguates the tool from all siblings.

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?

The description gives explicit guidance: it tells the agent this is for tagging rules (not the Keyword Monitor) and directs to use keyword_monitor_list for keyword search. It also names the replacement tool (tag_rule_list), making alternatives clear.

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