get_conversation

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

With no annotations, the description must disclose behavioral traits. It hints that 'optional comment and timeline embeds' affect the response shape, but it does not clarify whether the operation is read-only, whether authentication via api_token is required, or any rate limits or side effects. The agent cannot judge safety or side effects from this description.

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 sentence, directly front-loaded with the primary action ('Load a conversation') and relevant modifiers. No waste, and it is appropriately sized for the tool's apparent simplicity.

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 4 parameters (one obscure), no annotations, and a large sibling list, the description is too sparse. It fails to explain api_token, provide usage context, or disclose whether the operation is safe. The output schema exists but does not compensate for missing behavioral and parameter guidance.

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 0%, so the description must compensate. It clarifies that include_comments and timeline are optional embeds, but it leaves api_token completely unexplained. conversation_id is self-evident from the name, but the lack of explanation for a non-obvious parameter is a significant gap.

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 identifies the operation as loading a single conversation and mentions optional comment and timeline embeds, which distinguishes it from list-oriented siblings like list_conversations. However, it does not explicitly contrast with other conversation fetch tools (e.g., list_conversation_messages) to fully eliminate ambiguity.

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 offers no guidance on when to use this tool versus alternatives, no prerequisites, and no context about typical scenarios. It merely states what it does, leaving the agent to infer usage from the name and schema.

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