close_conversation

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates state. The description adds only the 'active' state qualifier; it does not say whether closing is reversible, whether history is preserved, or what happens to in-flight messages. Given annotation coverage, a moderate score is fair.

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?

A single short sentence, front-loaded with the verb and resource, with no wasted words. It is efficient, though arguably too terse for a destructive operation.

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 destructive mutation with no output schema, the definition omits prerequisites, reversibility, error/edge behavior, and any indication of what the result looks like. With only one undocumented parameter and no return contract, the agent is left to guess at important details.

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?

There is one parameter (conversation_id) with 0% schema description coverage, so the schema alone leaves the agent without guidance. The description does not clarify what ID is expected, where to obtain it, or whether it accepts other identifiers, so it fails to compensate for the coverage 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 gives a specific verb (close) and resource (conversation), so the action is unambiguous. However, it does nothing to differentiate this from siblings like list_conversations, get_conversation, or assign_conversation, which are all conversation-scoped.

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 phrase 'an active conversation' hints that the target must currently be open, but there is no explicit when-to-use guidance, no prerequisites (e.g. permissions, state), and no mention of alternatives or follow-up behavior. An agent gets almost nothing about when this tool is the right choice.

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