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

Annotations already establish the safe read-only, idempotent profile, so the bar is lower, and the description adds genuine value beyond them: every issue carries a fixUrl deep link into the SEO Expert app, and results are paginated. It stops short of describing ordering guarantees or what happens on an empty result set.

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, no filler, and the core purpose is front-loaded before filters and return-shape details. Every clause carries information the agent can act on.

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 an output schema present, return-value detail is not the description's burden, and annotations cover the safety profile; the description supplies the remaining essentials (scope, filters, pagination, fixUrl). Only the absence of sibling routing keeps it from being fully complete.

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 100%, so page, limit, ruleId, and the severity enum are all fully documented in the schema. The description restates the severity values and the limit ceiling but adds no new meaning such as rule-id format or severity interaction with ordering, so the baseline 3 applies.

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 ('List open SEO audit issues') plus the filter axes, so an agent immediately understands the tool's scope. It does not, however, distinguish itself from adjacent siblings like get_seo_summary, list_broken_links, or run_audit, which also surface audit-related data.

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 word 'open' and the optional severity/ruleId filters imply when the tool is useful, but there is no explicit when-to-use versus get_seo_summary or run_audit, and no stated preconditions (e.g. must an audit have been run first?). Usage is inferable rather than guided.

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