freelance_list_conversations

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

With no annotations, the description carries the full behavioral burden. It discloses the permission requirement ('Requires READ_OWN'), the return content ('unread counts'), and the thread-identity concept (anchors). It does not explicitly confirm read-only behavior, pagination, or ordering, but the permission and unread-count details add useful context.

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?

Three sentences, each earning its place: purpose and key data, permission, and disambiguation. The anchor explanation is dense but directly relevant to avoiding confusion between similarly named threads. No repetition or filler.

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 zero-parameter list tool with no nested objects or output schema, this is fairly complete: it states the permission, the returned data (threads with unread counts), and the anchor concept that addresses a common ambiguity. It only omits minor details like pagination or ordering.

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?

The tool has zero parameters with 100% schema description coverage, so there is nothing for the description to add about parameter syntax. Instead, it contributes conceptual value by explaining thread anchors, which helps an agent interpret the listed results.

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 clearly names the action ('list') and resource ('Message threads this account takes part in'), and adds the unread-count detail. It explains thread anchors for distinguishing conversations, but it doesn't explicitly contrast with the sibling freelance_get_conversation, so the distinction is inferred rather than stated.

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 implies its usage context: listing all conversations for the current account, versus viewing a single conversation or sending messages. However, it never explicitly says when to prefer this over alternatives like freelance_get_conversation, nor does it state exclusions.

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