update_conversation

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

Annotations only supply idempotentHint=true, and the description adds real value on top: metadata persists between messages and null clears it. However, for an update tool it omits whether a new metadata object replaces or merges with existing keys, which is the key behavioral ambiguity.

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?

Three short sentences, zero waste, and the core purpose is front-loaded before the usage note and the clearing rule. Nothing extraneous.

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 simple two-parameter tool with no output schema, full schema coverage, and an idempotency annotation, the description covers purpose, usage, and clearing behavior adequately. The only gap is replace-vs-merge semantics, which is minor here.

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 100%, with both parameters documented in the schema, so the baseline is 3. The description's note about passing null to clear metadata largely restates the schema's own 'or null to clear' description.

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?

States a specific verb ('Set') and resource ('metadata on a conversation'), and usefully narrows the broad name 'update_conversation' to a metadata-scoped operation. It does not explicitly contrast with siblings like get_conversation or list_conversations, but the scope is unambiguous.

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?

'Use this to store custom state, tags, or context that persists between messages' gives clear context for when the tool applies. There are no overlapping siblings to exclude and no explicit when-not guidance, so it stops short of a 5.

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