Get messages by conversation id

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destuctiveHint=false, so the safety profile is covered. The description adds the required OAuth scope 'conversations/message.readonly', which is useful authorization context, but does not disclose behavior such as default limit, pagination semantics, or result ordering.

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 and front-loaded, with the endpoint and scope appended compactly. It is not padded with fluff, though 'Get messages by conversation id' largely repeats the tool title and could have been replaced with more useful behavioral detail.

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?

Together with the fully documented schema and safety annotations, this is adequate for a simple read-only listing tool, but it omits any description of response format or pagination behavior despite there being no output schema. Auth scope and endpoint are present, which helps, but richer list-specific context would improve completeness.

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 parameters are already documented in the input schema. The tool description does not add extra meaning about conversationId, type, limit, or lastMessageId beyond what the schema provides.

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 messages by conversation id', and the endpoint makes the operation concrete. It is distinguishable from the sibling conversations_get_message by the plural resource and path. However, it does not explicitly clarify that this returns a list or that optional filters are available.

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 alternatives such as conversations_get_message, conversations_search_conversation, or conversations_export_messages_by_location. Sibling names imply differences, but the description itself leaves selection entirely to inference.

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