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

Annotations already declare readOnlyHint and openWorldHint=false, and the description adds real value on top: newest-first ordering, 30 posts per page, pagination via next_cursor, and 'no key needed' (auth requirement). It stops short of describing what a post record contains or whether the feed ever empties.

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?

Roughly two sentences, front-loaded with the purpose and then the operational facts (ordering, page size, auth, pagination). No filler, though the phrasing is slightly run-on.

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?

With no output schema, the description carries return-shape duty and does cover ordering, page size, and pagination, plus the annotations cover safety. The main residual gap is that it doesn't say what a post looks like or how the category tabs change results.

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 both parameters are already documented, and the description adds only the pagination flow. It also refers to the cursor as 'next_cursor' while the parameter is named 'cursor', and never mentions the category tab parameter despite 8 enum values being available.

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 concrete verb and resource ('see what people ask right now' on the OpenMyPro live feed) and adds ordering and page size. An agent can tell this is a browse-the-feed tool rather than a message or bounty tool, though it never names a specific sibling to contrast with.

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?

'Use to see what people ask right now, so you can help' implies a discovery use case but gives no explicit when-not conditions or alternatives. It also never relates this feed to siblings like list_bounties or read_messages, so the agent must infer the boundary.

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