create_snippet

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

With no annotations provided, the description must carry the behavioral disclosure burden. It only states the creation action and the optional parameters, plus the language default. It does not mention side effects, return behavior, authentication needs, whether prompt is used to scaffold code, or any other operational consequences.

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 description is a single, well-structured sentence that leads with the core action and immediately conveys optional parameters. Every word earns its place, with no redundant or filler content.

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?

This is a relatively simple tool with three optional parameters and no output schema. The description covers the core purpose and all parameters, making it minimally viable. However, the lack of annotations and absence of return-value or side-effect information leaves some contextual gaps for the agent.

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. The description adds value beyond the schema by clarifying that language defaults to 'javascript' (schema only says 'Defaults server-side') and by explaining that 'prompt' is a natural-language description of what the snippet should do. This provides useful semantic context for all parameters.

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 opens with 'Create a new snippet,' which is a specific verb+resource statement that clearly distinguishes this tool from siblings like update_snippet, duplicate_snippet, and delete_snippet. It also lists the optional fields (name, language, prompt), reinforcing what the tool does.

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?

Usage is implied by the verb 'create'—this tool is for creating new snippets rather than updating, duplicating, or deleting them. However, there is no explicit guidance on when to choose this over create-related siblings like duplicate_snippet, or any exclusions or alternatives.

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