create_snippet_note

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

No annotations are provided, so the description must fully disclose behavior. It states 'Save a code snippet as a note,' but fails to clarify side effects (e.g., overwriting, duplication), required permissions, idempotency, or postconditions. For a creation tool, this lacks sufficient transparency.

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 of 10 words with no redundant information. It front-loads the core purpose and omits filler, making it quick to parse.

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?

Despite a simple purpose, the tool has six parameters and no output schema or annotations. The description does not explain parameter usage, expected input formats (e.g., code snippet length), or return behavior. It is insufficient for an agent to use the tool reliably without additional context.

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?

The schema has 100% coverage of parameters, achieving the baseline of 3. The description merely echoes 'language tag and context' without adding syntactic constraints, valid formats, or relationships beyond what the schema already documents.

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 'Save a code snippet as a note with language tag and context' clearly specifies the action (save), resource (code snippet as a note), and key attributes (language tag and context). It effectively distinguishes this tool from siblings like create_note and create_dev_note by focusing on code snippets.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or suggest other tools for different scenarios. With multiple note creation tools, this omission hinders correct selection.

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