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

Annotations already cover the read-only, open-world, non-destructive profile. The description adds useful context beyond that: it states the return ordering, that the whole thread is returned, and that a Cotlet API key with access to the app is required.

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 purpose is front-loaded and the auth note is useful, but the second sentence repeats the first with nearly identical phrasing about the inquiry or booking it belongs to/is about. That duplication keeps it from being fully 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?

For a simple one-parameter retrieval tool with full schema coverage and annotations covering safety, the description gives enough context: thread contents, ordering, relationship to an inquiry or booking, and the auth requirement. No output schema exists, but the return shape is described sufficiently for correct invocation.

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 input schema has 100% description coverage and documents conversation_id, including that it comes from list_conversations. The description adds no parameter-level detail beyond what the schema already provides, so the baseline of 3 is appropriate.

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 gives a specific verb and resource: retrieve all messages in a conversation thread. It scopes the result as the whole thread, oldest message first, and ties it to the inquiry or booking it belongs to, which clearly distinguishes it from list_conversations and send_message.

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?

It gives clear usage context: the agent reads the thread before replying so it does not repeat an earlier answer. It does not explicitly name alternatives such as list_conversations, so it stops short of a full when/when-not/alternatives statement.

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