seerr_list_overriderule

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

The description does not disclose any behavioral traits beyond the readOnlyHint annotation. It does not mention whether this returns all rules, any pagination, ordering, or authentication requirements. It does not contradict the annotation, but it adds no value beyond it.

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 short and free of fluff, but it is under-specified and does not provide meaningful context beyond the tool name. It is not verbose, yet it fails to be a genuinely informative description.

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 zero parameters, read-only annotation, and presence of an output schema, the tool is simple and the description is not catastrophically incomplete. However, it lacks any explanation of what override rules are or how this listing is intended to be used, leaving some ambiguity for an agent.

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, so the description does not need to explain any parameter semantics. The empty input schema already fully covers the parameter surface, satisfying the baseline for a no-parameter tool.

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 'Get override rules' is essentially a paraphrase of the tool name 'seerr_list_overriderule' and adds no additional specificity. It restates the action and resource without clarifying what override rules are or what scope is covered.

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?

There is no guidance on when to use this tool versus the related create/update/delete overriderule tools. No context is provided about prerequisites, use cases, or situations where an alternative should be chosen.

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