get_assigned_conversations

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

No annotations are provided, so the description must disclose behavioral traits. It only states that the tool gets assigned conversations, without details on pagination behavior, output format, authentication requirements, or any side effects. The description adds minimal behavioral context beyond the obvious.

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 short but includes redundant lines (title repetition, API path, tags) that are unnecessary for an AI agent. It front-loads the purpose but wastes space on non-essential details. Could be more concise.

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 two optional parameters and no output schema, the description is incomplete. It fails to explain the return structure, how many conversations are returned, or any filtering beyond the assignment scope. For a tool retrieving dynamic data, more context is needed.

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%, with both parameters (page, page_size) fully described in the schema. The description adds no additional meaning or constraints beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 states the tool retrieves 'assigned conversations to current user', using a specific verb and resource. It distinguishes from sibling tools like get_unassigned_conversations and get_all_conversations by specifying the scope 'assigned to current user'.

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 name and description imply the tool is for retrieving conversations assigned to the current user, but no explicit guidance on when to use versus alternatives or when not to use is given. The differentiation is clear from context but not explicitly stated.

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