get_conversation_messages

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

No annotations are provided, so the description bears the full burden of disclosing behavior. The description only mentions pagination but does not state whether the operation is read-only, destructive, or requires authentication. Important details like rate limits, data freshness, or what happens with empty results are missing.

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 concise at 6 words, fitting a single sentence. It is front-loaded with the core action and resource. The brevity is acceptable but could be expanded slightly to include usage guidelines without becoming verbose.

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 there is no output schema and no annotations, the description should provide more context about the tool's behavior. It lacks information about what is returned, pagination limits, message ordering, or required permissions. For a tool with only 2 parameters and simple schema, it is under-specified.

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%, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides for the two parameters. It mentions pagination, which indirectly relates to the 'page' parameter, but does not clarify the relationship between page number and message ordering or other pagination details.

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 messages and specifies the resource as 'specific conversation' with pagination. It uses an active verb 'Get' and identifies a distinct resource. However, it doesn't explicitly differentiate from the sibling tool 'get_campaign_messages' which also retrieves messages.

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 provides no guidance on when to use this tool versus the many sibling tools, such as 'get_campaign_messages' or 'get_lead_conversations'. There is no mention of prerequisites, context, or scenarios where it should be avoided. The pagination behavior is mentioned but not explained in terms of usage.

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