ghl_conversation_get_messages

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

Annotations already declare readOnlyHint, idempotentHint, and not destructive. The description adds endpoint details, OAuth scopes, and pagination parameters, which provide some behavioral context beyond annotations but does not disclose return format or rate limits.

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 moderately concise but redundantly repeats 'Get messages by conversation id' twice. The additional line with endpoint, scopes, and pagination is useful but could be integrated more efficiently.

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 4 parameters, complete schema coverage, and no output schema, the description provides endpoint and OAuth scopes but lacks details on return format, error handling, or pagination behavior. It meets the minimum viable threshold but has gaps.

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%, so baseline is 3. The description mentions pagination params but adds no new meaning beyond what schema descriptions already provide. No additional parameter semantics are offered.

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 by conversation ID using a specific verb and resource. While it doesn't explicitly differentiate from siblings like ghl_conversation_get_message or ghl_conversation_get, the repeated emphasis on 'messages' (plural) and 'conversation id' makes the purpose clear.

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 guidance on when to use this tool versus alternatives (e.g., ghl_conversation_get_message for a single message). No mention of prerequisites or conditions where this tool should be chosen. The pagination note is present but insufficient for usage context.

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