manage_conversation

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

No annotations exist, so description must disclose side effects, statefulness, or constraints. It only says 'manage threading across sessions' but omits details like whether starting a conversation requires a topic, or that continuation is stateful. Behavioral traits are undercommunicated.

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 concise sentence front-loading the tool's purpose. However, it could be more specific while maintaining brevity (e.g., covering all actions). No wasted words.

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 8 parameters, no output schema, and no annotations, the description is too brief. It does not explain the flow between actions (e.g., 'start' returns a continuation_id, 'continue' uses it), or how parameters relate to actions. Users need to infer from schema alone.

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 100%, so baseline is 3. The description repeats action categories but does not add new meaning beyond the schema's parameter descriptions. It does not clarify optional combinations or defaults beyond what the schema already defines.

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 states it manages conversation threading and lists some actions (start, continue, search, analytics) but misses 'resume' and is vague with 'manage'. It does not clearly differentiate from sibling tools like 'ask' or 'get_analytics', which may overlap.

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 on when to use this tool versus alternatives (e.g., 'ask' for single queries, 'get_analytics' for standalone analytics). No when-not-to-use or prerequisites mentioned.

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