get_conversation

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

No annotations provided, so description solely informs behavior. It discloses search order (personal memory then library) but omits other traits like idempotency, error handling, or what happens if conv_id is not found.

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?

Two sentences with 12 words, no filler. Action verb first, efficient and front-loaded.

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 low complexity and presence of output schema, description covers basic operation but misses detail like uniqueness or encoding of conv_id. Gaps remain due to no annotations.

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 0%, yet description only restates 'by conv_id' without adding format, examples, or constraints. The parameter meaning is only trivially extended.

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 a full conversation thread using a conv_id, and specifies a two-step search order. However, it does not explicitly differentiate from sibling tools like get_conversation_summary.

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 implies when to use (need full thread by ID) and provides search order, but lacks explicit when-not-to-use scenarios or direct comparison to alternatives like list_recent_conversations.

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