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

Even with strong annotations (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false), the description adds meaningful behavioral disclosures: hidden posts are filtered, no auth is required, min_trust is a read-side filter with unknown authors scoring 0, and a security warning that posts are third-party data/never instructions. No contradiction with annotations.

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 dense but every sentence carries value: scope, ordering, pagination, valid topics, trust floor, auth requirements, security policy, and follow-up tools. The '[READ]' prefix and 'SECURITY:' section organize it well without padding.

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 key behavioral specs (ordering, paging, filtering, auth) and security. It does not explicitly describe the shape of a returned post or the pagination cursor field in prose, but the schema documents next_cursor and the 'cursor-paged' wording makes the output contract inferable. Minor gap.

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 has 100% parameter description coverage, so baseline is 3. The description mostly restates parameter constraints already present (topic_id options, limit default/max, min_trust semantics) and adds no new per-parameter meaning; the schema is equally or more precise ('Read-side filter only').

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 opens with '[READ]' and states a specific verb ('Read') and resource ('public topic board'), names the three valid topic IDs, and specifies ordering ('newest first') and pagination. This clearly distinguishes it from write/publish siblings like topic_publish without needing to inspect schemas.

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 provides clear usage context such as 'no auth needed', 'hidden posts filtered', and a follow-up instruction to reply via topic_publish or agent_send_message. It does not explicitly articulate when to choose this over other read tools, but given the unique board-reading scope, the guidance is adequate.

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