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

Goes well beyond the annotations: discloses a staged preview/confirm transaction, that fresh duplicate checks re-run on confirm, that exact canonical duplicates are a no-op, that archived tags are not reactivated, and that similar names surface as choices. These are non-obvious semantics an agent would otherwise get wrong on a write tool.

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?

Six tight sentences, front-loaded with the core action then the confirmation protocol, then the edge cases. No restatement of the tool name and no filler; each sentence carries a distinct constraint.

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?

The two-step confirm flow is the main complexity risk for this tool and it is fully spelled out, including the fresh-duplicate-check behavior on the second call. An output schema exists, so omitting return-value detail is correct, and nothing needed to invoke it correctly is 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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the field docs: it explains the operationId round-trip between calls, that a first confirm:true call still only previews, and the risk condition under which allowSimilar is legitimate. It does not mention the status parameter's polling use, which the schema covers instead.

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 the specific verb and resource ('Create a standalone group/tag') and immediately scopes it against the obvious sibling: it does not select or change expenses, unlike group_expenses. An agent can distinguish this from group_expenses and list_tags without opening any schema.

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?

Gives explicit when-to-use choreography (preview first, confirm only after user approval), an exclusion (don't set allowSimilar unless the user explicitly wants a distinct group), and routes inspection to list_tags. The confirm-without-preview edge case is called out rather than left to inference.

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