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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is covered. The description adds genuinely new behavior: results come in evaluation order, each row carries trigger/action/state/priority/cooldown/daily cap, and pagination uses an opaque cursor. Minor gap: no statement of the default page size or default active_only behavior.

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 what is listed and in what order, then the get_bot caveat, then pagination. No filler and nothing repeated from the schema or annotations.

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?

An output schema exists, so the field enumeration is a bonus rather than a requirement, and the get_bot pointer and cursor note round out a simple read tool well. The only real shortfall is that the two optional filter parameters are never explained, which leaves an agent guessing about narrowing results.

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 0%, so the description carries the full burden for three parameters, but it only glosses one — cursor is called "opaque," which is useful. It says nothing about limit (bounds 1-50) or active_only, so two of three parameters remain semantically undocumented anywhere.

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 a specific verb and resource ("Lists every auto-reply rule") plus the scope "all action types" and the ordering ("evaluation order"). It also distinguishes itself from get_bot by saying AI rules show the bot name rather than the persona, so an agent can tell the two apart without opening a schema.

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 routing hint is explicit: when you need the persona behind an AI rule, use get_bot instead. What is missing is any guidance on the optional filters — nothing says when to use active_only or how many rules a typical page returns, so the agent must infer filter usage.

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