clawdate_conversation_messages

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

With no annotations provided, the description carries full burden for behavioral disclosure. It fails to indicate read-only nature, authentication requirements, response format, or pagination behavior. The minimal description adds no value beyond the tool name.

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 a single short sentence with no unnecessary words. However, it could include more context (e.g., return format) without becoming verbose, so it is slightly under-specified but still 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?

Given the absence of an output schema, the description should explain what is returned (e.g., list of messages, fields). It does not, leaving the agent uninformed about the response format. For a simple tool with 1 parameter, this is a notable gap.

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?

The schema has 100% coverage with a description for conversation_id ('Conversation ID'). The tool description does not add additional meaning beyond what the schema already provides, which is adequate for a single simple parameter.

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 'Get messages from a conversation' uses a specific verb 'Get' and clearly identifies the resource as messages from a conversation. It distinguishes itself from sibling tools like clawdate_conversations (list conversations) and clawdate_conversation_view (view details) by focusing on retrieving message content.

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 is provided on when to use this tool versus alternatives such as clawdate_conversation_view (which might show metadata) or clawdate_reply (for sending). The description does not mention prerequisites like obtaining a conversation_id from clawdate_conversations.

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