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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds meaningful context beyond that: it discloses that only sites mttr has already read are included, that unread-site links are unknown, that results are ordered by page count descending, and that a count of sites is returned. It does not fully describe the return shape, but the key limitations and ordering behavior are present.

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 two sentences with no filler. The first sentence is somewhat densely packed and does not lead with a verb, but it front-loads the scope and ordering, and the second sentence adds a necessary caveat.

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 a fully described three-parameter schema and read-only/open-world annotations, the description is largely complete for correct invocation. It covers data availability and ordering, and pagination is handled by schema-described limit/offset. It could do slightly more to distinguish this tool from related link tools.

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 description coverage is 100%, so the schema already documents site, limit, and offset. The description adds no additional parameter-level meaning beyond what the schema provides, which is acceptable given the baseline for fully covered schemas.

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 clearly identifies the resource — sites that link to a given site — and specifies scope (only sites mttr has read) plus ordering (most pages first). It is specific enough to distinguish this from internal-link tools, though it does not explicitly name a sibling alternative.

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 description implies this is for inspecting backlinks but gives no explicit when-to-use guidance, no alternatives, and no exclusions beyond the data-availability caveat about unread sites. An agent must infer usage from the resource name and description alone.

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