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

The description says 'Reads sites only and changes nothing,' while the annotations set readOnlyHint=false. That is a direct contradiction, even though the description otherwise provides useful caching, concurrency, and rate-limit details.

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 purpose is front-loaded, but the description is a dense run-on with repeated 'run.limited is then true' clauses. The caching, quota, and scoped-check details are useful but would be easier to parse if structured more cleanly.

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 complex tool with caching, concurrency, daily quotas, and per-site limits, the description covers the operational behavior well. It does not describe the returned audit data, and the annotation contradiction remains a material gap.

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 schema already documents site_ids at 100% coverage, but the description adds substantial semantics: it explains that scoped checks leave other sites alone, do not update last_run_at, do not consume daily on-demand passes, and are capped at 12 per site per day.

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 opens with a specific verb and resource: 'Run the SEO audit now across every connected site.' It also clarifies the scope by saying it ignores the daily schedule, so the agent can distinguish an on-demand audit from the scheduled audit.

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 explicitly says when to offer the tool: only when results are over a day old or the user asks. It also explains the scoped site_ids use case, but it does not name a sibling alternative for comparison.

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