get_all_conversations

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

With no annotations, the description must fully disclose behavior. It is a read operation, but this is not explicitly stated. The description does not mention authentication requirements, rate limits, pagination behavior (e.g., default page size, max results), or whether it returns all conversations across teams. The minimal text 'GET /api/v1/conversations/all' leaves too much implicit.

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 very concise, consisting of three short lines. While it is front-loaded with the purpose, it sacrifices informativeness. Every sentence earns its place, but there is opportunity to add value with minimal extra text.

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 the tool has no output schema, the description should explain what is returned (e.g., list of conversations, pagination metadata). It does not. For a tool with two optional pagination parameters, the lack of detail on response structure or scope (e.g., 'all conversations in the system') makes it incomplete.

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?

Since schema description coverage is 100%, the description adds no additional meaning beyond what is already in the schema. Both parameters (page and page_size) are already documented with descriptions in the input schema. The tool description does not clarify their usage or relationships.

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 'Get all Conversations', indicating the resource and action. However, it does not differentiate from siblings like get_assigned_conversations or get_unassigned_conversations, which have similar names and purposes. The addition of the endpoint path provides some specificity.

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 guidelines are provided. The description does not specify when to use this tool versus alternative conversation retrieval tools, such as get_assigned_conversations, get_unassigned_conversations, or search_conversations. This lack of context forces the agent to guess based on names alone.

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