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

Beyond the annotations, it discloses live-feed cursor behavior, activity-driven reordering, filter/pagination ordering, and the fact that counts measure unread conversations rather than events. These are meaningful, non-obvious behaviors, though the absence of an output schema leaves the broader result shape unexplained.

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?

Four short sentences front-load the resource and then efficiently cover filtering, cursor, and count semantics without filler. The wording is dense but appropriately sized for a three-parameter feed-listing tool.

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?

The description covers the main non-obvious behaviors needed to paginate and interpret this live inbox, while the schema supplies defaults and bounds. Undefined tab semantics and the lack of explicit differentiation from notification and event siblings leave modest but real gaps, especially given the absent output schema and parameter descriptions.

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?

With 0% schema description coverage, the description usefully explains cursor semantics and implies that tab filters are applied before pagination. It never explains the five tab values or directly defines limit and cursor as page-size and continuation inputs, so its compensation for the undocumented schema is only partial.

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 opening sentence identifies the exact resource and its granularity: one inbox conversation per pull request, document, or issue activity family. This clearly conveys a grouped conversation view rather than a generic activity list, although it does not explicitly differentiate the sibling notification and event tools.

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 gives concrete operational guidance: filters run before pagination, and a fresh first page should be fetched to reconcile conversations moved by new activity. It does not explain when to choose this tool over list_notifications or list_inbox_conversation_events, so alternative-selection guidance remains incomplete.

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