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

Annotations already state readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behavioral details: ties share places, counting is based on site reports, anonymous sites use codes, and drafts/crawler-blocked sites are excluded. It could still say more about result consistency or limits, but it is substantially informative.

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 a dense run-on with awkward quoted parameter references and repetitive phrasing. It contains relevant information but is hard to scan and not structured for quick agent comprehension.

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 does a reasonable job covering return content: stages, pages read, prior score, record-mode outputs, and what records are counted over. It also covers exclusions and anonymization, making it fairly complete for a complex leaderboard tool, though clarity suffers.

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 the baseline is 3. The description adds meaning beyond the schema by explaining record enum values and how filters can be combined, though the awkward phrasing around 'in', 'record', and place counts reduces precision.

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 public leaderboard of ranked sites scored by their latest read and describes filter and record modes. It is specific enough to distinguish this as a leaderboard/list tool, but the dense phrasing and lack of explicit sibling differentiation keep it below a 5.

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 explains how filters and the record parameter change the output, including record alternatives like fastest, improved, stages, answer-first, and biggest. However, it gives no explicit guidance on when to use this tool versus siblings such as mttr_sites, mttr_search, or mttr_compare.

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