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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds useful context that results are scoped to 'this account' and include the last message per workstream. It says nothing about pagination, ordering, or result volume, which are the remaining behavioral unknowns.

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?

One short sentence, front-loaded with the resource, with the parenthetical placed exactly where clarification is needed. No waste, though it reads as a fragment rather than a complete statement of behavior.

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 read-only list tool with full schema coverage and annotations, the description covers what it returns at a high level. It omits pagination behavior and result ordering, which matter for an agent deciding whether to page through a conversation list.

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?

Only one optional parameter and the schema documents it at 100% coverage with an explicit 'next_cursor from the previous call' description. The description adds nothing about the cursor, so baseline 3 applies.

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?

Names the resource (WorkStreams) with a clarifying parenthetical that a WorkStream is a conversation with a hired freelancer, and adds that each entry carries the last message. An agent can tell this is an account-scoped conversation listing, distinct from project/offer/freelancer listing siblings. Not fully 5 because it doesn't state ordering or scope limits.

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?

No statement of when to call this versus the many other list_* and get_* siblings, and no mention that it paginates or when to continue with the cursor. The agent is left to infer usage entirely from the name.

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