get_assigned_conversations

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

No annotations are supplied, so the description carries the full burden. It does disclose a real operational prerequisite ('Requires the conversations:read_assigned permission') and the GET endpoint implies a read-only, non-destructive call, but it says nothing about pagination defaults, result ordering, or what happens when the user has no assigned conversations.

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 core sentence is front-loaded and useful, but the leading 'Get Assigned Conversations' restates the tool name and 'Tags: Conversations' is metadata noise. The raw endpoint path is mild filler given the tool name already conveys the resource.

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?

With five optional parameters fully covered by the schema and no output schema, the description only needs to establish scope and prerequisites, which it does. It is incomplete on return behavior — no mention of pagination envelope, default page size, or empty-result handling — which matters for a list endpoint an agent will page through.

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 100%, with page, page_size, order, order_by, and filters all fully documented including enum values and filter syntax, so the schema does the heavy lifting. The description adds no parameter meaning beyond that, which is the baseline expectation here.

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 ('Get all assigned conversations') and narrows the scope to 'current user', which distinguishes it from the unassigned/team siblings in the catalog. It stops short of naming an alternative explicitly, so it is clear but not fully differentiated.

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?

Usage is implied by the scope phrase 'assigned to current user' — an agent can infer this is the tool for the caller's own queue — but there is no explicit when-to-use, when-not-to-use, or pointer to get_all_conversations / get_unassigned_conversations for other scopes.

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