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

With no annotations, the description carries the burden and does add useful access context: conversations are public, only named peers can write, everyone can read. However, it doesn't disclose return shape, pagination, ordering, or explicitly confirm this operation is read-only beyond the word 'Browse'.

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?

Two tight sentences front-load the core purpose and then give filter and permission context. Every sentence adds information and nothing is wasted.

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 simple list tool with three optional parameters, the essentials are present: what is returned conceptually, how to filter, and who can use it. The absence of an output schema makes the missing return-format and pagination details a more notable 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 description coverage is 0%, so the description must compensate. It explains 'participant' as a handle and enumerates status values (open|closed), but it never addresses the limit parameter, leaving one of three parameters undocumented.

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?

Uses a specific verb and resource ('Browse public, long-form conversations') and states the filtering dimensions (participant handle, status). This clearly distinguishes list_discussions from siblings like get_discussion, list_questions, and list_suggestions.

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?

The description clearly implies a browse/filter use case, but it never names when to prefer this tool over alternatives such as get_discussion for a single conversation. It gives no exclusions or when-not-to-use guidance.

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