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

With readOnlyHint, destructiveHint=false, and openWorldHint already in annotations, the description adds useful behavior: ordering ('most recent first'), the contents of each item ('buyer, project and a preview of the last message'), the effect of awaiting_reply, and an auth requirement ('Needs the user's Cotlet API key...'). It does not cover rate limits or pagination behavior beyond the cursor parameter, hence a 4 rather than 5.

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?

The description is appropriately sized overall and mostly front-loads the actionable information, but the opening sentence ('PeoplePerHour: Your WorkStream threads with buyer, project and the last message.') is a redundant fragment that duplicates the title and the following sentence. Removing it would make the definition tighter, but the remaining content is efficient.

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?

Given that annotations cover the safety profile and the input schema fully documents all three parameters, the description supplies the remaining context an agent needs: it explains what is returned ('buyer, project and a preview of the last message'), the ordering, the filter behavior, and the API key requirement. No output schema exists, but the description adequately covers return values, so nothing critical is missing.

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 the baseline is 3. The description's mention of awaiting_reply ('Set awaiting_reply to see only threads where the buyer wrote last') largely restates the schema description ('Only threads where the buyer sent the last message') and adds no new syntax or format detail for limit or cursor.

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 specific verb and resource: 'Lists your WorkStreams, most recent first, each with the buyer, the project and a preview of the last message.' It also distinguishes this list tool from get_workstream by explaining that the workstream_id from these results should be used with that tool. This is enough for an agent to identify the tool's purpose among siblings.

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 provides clear usage context: set awaiting_reply to filter to threads where the buyer wrote last, and it tells the agent to use the returned workstream_id with get_workstream, send_message, and create_invoice. However, it does not explicitly state when to use this list versus other list tools (e.g., list_offers, list_proposals) or any exclusions, so it falls short of a 5.

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