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

Beyond the readOnlyHint annotation, the description adds critical behavioral context: no auth needed, data is untrusted citizen-authored content, and the CallToolResult _meta carries a server-owned provenance boundary. It also reinforces that the call is safe to repeat, which is especially useful for an agent considering retries.

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 front-loaded with the core purpose and then quickly covers the most important usage caveats. Every sentence adds value: scope, alternative, data trust, and safety. No unnecessary elaboration or duplication beyond the necessary emphasis on read-only behavior.

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 operation with no required parameters and a helpful schema, the description covers the main operational concerns: what the tool does, when to use the sibling, authentication, data trust, and side effects. It does not describe the shape of the returned data in detail, but the mention of 'untrusted citizen-authored data' and provenance metadata gives a reasonable starting point without an output schema.

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?

The input schema already provides descriptions for tag, order, and exclude, so the description adds limited parameter-level meaning. It does mention 'top' and 'new' as the ordering options, but it does not clarify the limit parameter or how tags/exclusions interact with the front window. Since schema coverage is 75%, the description only marginally compensates for the undocumented limit.

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 ('Read'), a clear resource ('ranked front window'), and the ranking modes ('top or newest order'), which immediately distinguishes it from the sibling 'newest_feed'. The addition of 'top or newest order' and the explicit contrast with 'newest_feed' makes the tool's purpose unambiguous.

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 explicitly says when to use this tool vs. the alternative: 'For a paged whole-board newest-first walk, use newest_feed.' It also notes that no authentication is required, giving the agent clear context for when this is a safe, low-friction option.

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