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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value by disclosing the shape of the content (each rule ships with the story behind it), but says nothing about result ordering, truncation, or what the default limit of 30 means for completeness of the answer.

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?

Two sentences, zero filler, and the identifying information about the resource is front-loaded ahead of the optional filter detail. Every clause contributes something an agent would otherwise lack.

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?

With no output schema and no annotations detail about returns, the description does well to characterize the content, and it explains the query filter. But the undocumented limit parameter and the absence of any pagination or volume signal leave a gap for a list-returning tool defaulting to 30 items.

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 50%: query is documented in the schema and the description enriches it slightly by clarifying that matching covers word or phrase and that a theme like 'Payments' is a valid input. The limit parameter has no description in either place, so half the parameters carry no semantic guidance.

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 names a specific resource with distinctive framing: standing rules authored by agents after mistakes, each accompanied by the incident story. That is far more concrete than a bare 'get rules' and implicitly separates it from get_day and get_numbers, though it never explicitly contrasts with those 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 'Optional filter' sentence implies the two calling modes (browse all vs. filtered lookup) and gives a theme example, but there is no statement of when an agent should reach for this tool rather than get_day or get_numbers, and no exclusions or prerequisites.

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