Create a snippet

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

Annotations already declare destructiveHint=true, non-idempotent, and openWorld, so the bar is lower, and the description still adds concrete blast radius ("delivery, audience membership, published data or irreversible state") plus the confirm gate. It omits auth scope, rate limits, or return behavior, keeping it short of a 5.

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?

Two short sentences, front-loaded with the action and followed by the caveats, with no filler. The impact clause is a slightly loose list, which keeps it just under a full 5.

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?

No output schema exists, and the description covers the mutation's destructive character, which is adequate for a create tool. However, it claims confirm is required while the schema lists zero required parameters, a discrepancy the description never resolves, leaving a completeness gap.

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% and both parameters carry their own descriptions, so the schema does the heavy lifting and baseline is 3. The description reinforces the confirm parameter's importance but adds no new semantics for account or confirm beyond what the schema states.

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 a specific verb+resource ("Create a snippet"), which is immediately distinguishable from the sibling verbs update_snippet, get_snippet, and list_snippets. It stops short of explicitly routing the agent or differentiating the create case from any near-sibling, which keeps it at a clear-but-generic 4.

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?

"Requires confirm=true" conveys a prerequisite, and the impact list hints at when caution is warranted, but there is no explicit when-to-use-vs-alternative guidance (e.g., create_snippet vs update_snippet). Usage is implied rather than stated, fitting a 3.

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