toggle_snippet_permanent

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 notes '[mutation]' implying a write operation, but fails to specify side effects, reversibility, or required permissions. The description is too brief to inform an agent about the behavioral impact.

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 very short and front-loaded with the action. However, the '[mutation]' tag is somewhat informal and reduces clarity. Every sentence earns its place, but the structure could be improved by integrating the tag naturally.

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?

Given the simplicity of the tool (one parameter, no output schema), the description is nearly adequate. It explains the core action and effect, but lacks context about the snippet's state, prerequisites, or reversibility. Compared to sibling tools with more detailed descriptions, it is complete enough to use but not robust.

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 input schema has 100% description coverage for the single parameter 'id', so the schema already documents its meaning. The description adds no additional context beyond what the schema provides, so baseline score of 3 is appropriate.

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 clearly states the action ('toggle permanent'), the resource ('snippet'), and the effect (protects from age expiration). However, it does not differentiate from sibling tools like toggle_knowledge_file, which also toggle a boolean state on knowledge resources.

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?

No guidance on when to use this tool versus alternatives. It does not mention any prerequisites, limitations, or scenarios where this tool is appropriate. The description only states what the tool does, not when to use it.

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