st.chat.metadata.patch

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

With no annotations, the description must disclose side effects; it only notes that confirm=true is required. It doesn't state whether the patch is destructive/reversible, how force or unset alter behavior, or what happens on failure.

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 single sentence is tight and front-loaded, with no wasted words. However, brevity comes at the cost of critical detail.

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 7-parameter nested-object mutation tool with no output schema and no annotations, this is far too thin. Core operational semantics for force, confirm, unset, updates, and snapshotLabel are missing.

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%, and the description adds only the 'dotted paths' clue. Seven parameters including force, unset, updates, and snapshotLabel are left entirely unexplained.

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 ('Patch') and resource ('chat_metadata dotted paths' in a specific ST chat file). It distinguishes the target from generic patch tools like st.resource.patch, though it doesn't explicitly name sibling tools.

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 choose this over st.chat.metadata.get, st.config.patch, or st.mvu.chat_state.patch. The only operational note is 'Requires confirm: true', which is a precondition, not usage context.

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