Get Maintenance Report

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

readOnlyHint=true already covers the safety profile, so the bar is lower, and the description still adds real context: the report reflects a previously run scan, the staleness threshold is roughly 6 months, and the intended downstream action is remediation via the sandbox. It does not disclose size limits, whether the report can expire, or permission requirements.

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 waste, and the tool's contents are front-loaded ahead of the usage hint. Each clause carries information an agent would otherwise have to infer.

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, the description carries the burden of explaining return contents, and it does so by naming the three issue categories. What is missing is the report's freshness/expiry semantics and whether run_maintenance_scan must precede it — modest gaps for an otherwise well-covered zero-parameter read tool.

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 takes no parameters, so the baseline is 4. The description correctly implies no filtering or scoping inputs are needed, which is consistent with the empty schema.

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+resource: retrieving the latest site-health scan report, and enumerates exactly what it contains (stale pages, missing meta descriptions, lingering drafts). The word 'latest' implicitly distinguishes it from the sibling run_maintenance_scan, which generates a fresh scan rather than reading the existing one.

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?

Explicitly frames the tool as a work queue and routes the agent to the sandbox workflow for fixing the issues it surfaces. It gives clear context for when to call it, but never states the alternative case — e.g. that run_maintenance_scan must be invoked if the report is stale.

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