list_muting_rules

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

No annotations are provided, so the description must convey behavioral traits. It correctly implies a read-only operation ('List'), but fails to disclose pagination, rate limits, or whether it returns all rules without filtering. The description is bare minimum for transparency.

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 a single sentence with no wasted words. It is front-loaded with the action and resource, and efficiently conveys the tool's purpose.

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, output schema, or annotations, the description is minimally sufficient but lacks details about scope (e.g., are these all rules for the whole account?), pagination, or ordering. For a simple list tool, basic completeness is achieved, but more context would improve agent understanding.

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?

Since there are no parameters, the description adds value by explaining that the output includes conditions and schedules, compensating for the lack of parameter documentation. Schema coverage is 100% (no params), so the baseline is high, and the description enhances understanding of the result.

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 the action (List) and resource (muting rules), and adds specificity with 'in the account with their conditions and schedules', effectively distinguishing from sibling tools like create_muting_rule or delete_muting_rule.

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 provides no guidance on when to use this tool versus alternatives (e.g., create, update, delete), nor does it mention any prerequisites or limitations. A simple read tool may not need extensive guidelines, but the lack of context about scope or filters leaves room for ambiguity.

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