Create a snippet

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

Adds genuine context beyond the annotations by naming the affected domains (delivery, audience membership, published data) and irreversible state, plus a confirm requirement. Annotations already flag destructiveHint=true, but the description specifies what is at risk, which is useful.

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, front-loaded sentences with the verb+resource first and the constraint last. No filler, though the effect enumeration is slightly broad ('May affect...').

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 zero-required-param mutation tool with no output schema and full annotation coverage, the description covers the key risk profile and the confirm gate. Nothing critical is missing for correct invocation.

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%, so both account and confirm are already documented in the schema. The description only restates the confirm requirement, adding little beyond the structured field.

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 (Create) and resource (snippet), clearly distinct from the sibling update_snippet, list_snippets and get_snippet. It doesn't explicitly name which sibling to use instead, so it stops short of 5.

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 a conditional usage rule — confirm=true and only for user-requested actions — but no explicit when-to-use-vs-alternatives guidance relative to update_snippet. Usage is implied but not fully scoped.

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