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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description's 'Read only' adds nothing beyond them. It does add useful context about the returned rule types, scopes, and recipient counts, but provides no further operational details such as pagination or empty-result 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?

The compact statement front-loads the resource and then efficiently summarizes its types, scopes, and recipient-count output. The final 'Read only' is redundant with the annotations but adds negligible bulk.

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 simple read-only listing with two optional, fully documented parameters, the description and schema provide enough information to select and invoke the tool correctly. Because there is no output schema, the description's summary of rule types, scopes, and recipient counts is especially useful for setting result expectations.

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 100%, and both parameters already explain company selection, the default company, and inclusion of paused rules. The description's generic reference to 'the company's' rules adds no meaningful parameter guidance, making the high-coverage baseline of 3 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 precisely identifies the resource as a company's email alert rules and usefully enumerates rule types, scopes, and recipient counts. Although phrased as a noun phrase rather than with an explicit list verb, its subject matter clearly distinguishes it from siblings that retrieve shipments, carriers, companies, or tickets.

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?

It provides clear context for inspecting notification-rule configuration rather than shipment status or events. It does not give explicit when-not guidance or name an alternative tool, so it falls short of a 5.

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