create_snippet_note

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic write operation ('save'), omitting details about side effects, idempotency, authentication needs, or return behavior. This is insufficient for a mutation 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?

The description is a single sentence with 10 words, making it concise and front-loaded. However, the extreme brevity sacrifices some clarity and completeness, which slightly reduces the score from 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?

With 6 parameters, no annotations, and no output schema, the description fails to cover critical context such as return behavior, prerequisites, or error conditions. It is too minimal to enable correct invocation without further exploration.

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 no additional meaning to parameters beyond the schema; it merely summarizes them ('language tag', 'context'). It does not provide constraints, formats, or usage examples.

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' uses a specific verb ('save') and clearly identifies the resource (code snippet as a note). It distinguishes from siblings like create_note (general) and create_dev_note (developer-focused) by explicitly targeting 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 implies usage for saving code snippets but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives (e.g., create_note for non-code notes) or context for selecting this tool.

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