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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered externally. The description adds useful behavioral context by saying the result includes both failed rules and their fixes plus inbound/outbound links, but it does not clarify pagination, freshness, permissions, or limitations.

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 definition is a single front-loaded sentence that avoids repetition. It is efficient, though the compressed phrasing of 'what it says about itself' and 'rules it fails with the fix for each' makes some of the content less immediately clear.

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 values. It names the major categories (page self-description, failed rules and fixes, inbound/outbound links), which is helpful, but it remains vague about the exact representation and whether full page content, metadata, or limited summaries are returned.

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%, and both required parameters are already documented in the input schema with examples: 'path' as /guides/gravel and 'site' as example.com. The description adds no parameter-level detail beyond the schema, so the baseline of 3 is appropriate.

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 identifies a specific resource, 'one page of a site,' and enumerates its contents: self-description/metadata, failed rules with fixes, inbound links, and outbound links. It is more specific than the title alone, though it uses somewhat literary phrasing such as 'what it says about itself' instead of explicit terms like metadata or page content.

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 alternatives such as mttr_pages, mttr_backlinks, mttr_links, or mttr_rules. The description implies it returns page-level detail, but it does not state when that is preferable to sibling tools or mention any prerequisites.

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