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. The description adds useful context about the returned fields and the 'sites mttr has read' scope, but it does not discuss pagination defaults, sort behavior, or authorization boundaries.

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 single front-loaded sentence with zero waste. It states the action, scope, and return summary immediately.

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 a fully described six-parameter schema and read-only annotations, the description provides a good high-level picture of what the tool returns. It omits some list-tool details such as default sorting and pagination semantics, but these are partly covered by the schema and there is no output schema to explain.

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%, and all six parameters including the three enums are documented directly in the schema. The description adds no parameter-specific meaning beyond the return fields, so the schema does the heavy lifting as expected for a baseline 3.

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 states a specific verb and resource: it lists the sites mttr has read, and adds the return fields (latest score, page count, rule to fix first). It is clear what the tool does, though it does not explicitly distinguish itself from the singular mttr_site or other list-like siblings.

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 usage by saying it lists sites mttr has read, so an agent can infer this is the plural overview tool. However, it gives no explicit when-to-use guidance, no exclusions, and does not name alternatives such as mttr_site for single-site detail.

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