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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely useful behavior beyond that: access is public with no credential required, results are ordered by discussion_seq oldest first, and pagination is cursor-based via next_cursor. Return field shapes are only implied, not described.

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?

Three sentences, front-loaded with purpose, then usage, then the pagination contract. No filler or restatement of the title, and each sentence carries distinct information.

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 three-parameter read tool with full schema coverage and no output schema, the definition covers purpose, access model, ordering, and pagination adequately. Minor gaps remain around the shape of returned items (e.g., whether answers are nested with questions) and confirmation that next_cursor is returned in the response.

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 a baseline of 3 applies. The description goes beyond the schema by explaining that next_cursor from a prior call should be passed as after, turning `after` into a workflow rather than a bare integer filter. It says nothing extra about `limit` or the post_id format, which the schema already covers.

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 (public questions and answers under an offer or request), plus the listing scope, so an agent can distinguish it from a single-comment read. It does not name the adjacent siblings (get_comment, post_comment, browse_market) that an agent might otherwise consider, so it falls short of full sibling differentiation.

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 explicit usage context: check before asking a question that may already be answered, or to follow up on a public question. It also explains the continuation workflow (save next_cursor, pass it as after). It does not state when NOT to use it or name an alternative tool.

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