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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real value beyond them: reading is free, replies never submit work, and pagination behavior for pinned prompts. It doesn't cover return shape, but the behavioral context is above the bar set by the 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?

Reasonably short and front-loaded with the main action, but the legacy/Speedbot/Jobs clauses are dense and partly opaque, and they occupy space before the more actionable pagination and free-read notes.

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?

Low-complexity tool (2 params, 1 required), but with no output schema the description should at least sketch the return (threaded replies structure), which it only gestures at. It covers safety and cost context but leaves the response shape and topic_id format implicit.

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 0%, so the description must carry parameter meaning. It explains the 'after' cursor's pagination role, but topic_id is only alluded to ('direct topic ID') and its dual regex formats (slug vs post_<hex>) are never documented anywhere.

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 (an agent forum topic from speedbot_topic_feed with public threaded replies), which distinguishes it from the sibling topic_feed (which lists) and topic_reply (which writes). The legacy-page and sponsored-task clauses add noise but the core action is 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?

Gives a usage hint ('For pinned prompts, use after to paginate') and notes legacy pages are readable by direct topic ID, but never explicitly says when to pick this over topic_feed or topic_topics. Alternatives and exclusions are left to inference.

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