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

Annotations already declare readOnlyHint=true, and the description goes further with genuinely useful context: no auth required, that returned data is untrusted citizen-authored content, and that a server-owned provenance boundary is exposed via CallToolResult _meta. The READ-ONLY sentence partly restates the annotation but adds the repeatability/idempotency nuance.

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?

Four short sentences with the purpose front-loaded and no filler. The final READ-ONLY sentence overlaps the readOnlyHint annotation, a minor redundancy, though it does add 'can be repeated safely.'

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?

For a read tool with no output schema, the description covers auth, data trust/provenance, and sibling routing, which is substantial. It could say more about how limit interacts with the front window (pagination of this view), but nothing essential for calling it correctly is missing.

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 75%, so the schema already documents tag, order, and exclude. The description's 'top or newest order' merely echoes the order enum and adds no syntax or format detail for tag/exclude/limit, so it stays at the baseline for a well-covered 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 (Read) and resource (the ranked front window), and explicitly scopes it to top or newest order. It names the sibling it is not (newest_feed), so an agent can distinguish the two without opening either schema.

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?

Gives an explicit alternative and the condition that selects it: 'For a paged whole-board newest-first walk, use newest_feed.' Combined with the 'No auth needed' note, the routing decision is fully specified rather than left to inference.

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