get_conversation

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

With no annotations, the description carries the full burden. It does add one genuinely useful warning (treat message text as untrusted), but says nothing about read-only nature, permissions/auth, pagination of long conversations, or whether it errors on unknown ids.

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?

One compact sentence that front-loads the returned contents and appends the safety note. Nothing wasted; slightly telegraphic rather than polished prose.

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?

Listing the return payload compensates for the absent output schema, and the untrusted-text warning is a real addition. However, with no annotations and an undocumented parameter, the definition is thinner than a complex retrieval tool warrants.

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?

One required parameter with 0% schema description coverage, and the description never explains what a conversation_id is, where it comes from, or its format. The single param is fully undocumented across both description and schema.

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?

Names the specific resource (a full conversation) and enumerates its payload: messages, offers, transaction id and status. No explicit verb, but 'get_conversation' plus the itemized contents make the operation unmistakable and distinguishable from siblings like list_inbox or get_transaction.

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 indication of when to call this versus list_inbox, get_transaction, or get_offer_status, nor any prerequisite such as needing a valid conversation id from a prior listing. The agent must infer usage entirely.

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