edit_knowledge_snippet

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. The tag '[mutation]' implies modification, but there is no information about side effects, required permissions, reversibility, or whether partial updates are allowed.

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 (one line) and conveys the purpose quickly. However, it lacks structure (no headings, no separation of concerns) and does not provide any additional context beyond the bare minimum.

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 lack of output schema and annotations, the description should provide more context about behavior, but it only offers a minimal purpose statement. For a mutation tool with 3 parameters, more details on usage constraints or outcomes are needed.

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 its 3 parameters (id, content, category). The description restates that it edits content and category, adding no new meaning beyond what the schema already provides. 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 it edits content or category of a knowledge snippet ('Edita el contenido o categoria de un snippet de conocimiento'). The verb 'editar' and resource 'snippet de conocimiento' are specific. It distinguishes from sibling tools like delete_knowledge_snippet or create_knowledge_file, but does not explicitly mention that it modifies existing 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?

No usage guidance is provided. The description does not indicate when to use this tool versus other snippet-related tools (e.g., create_knowledge_snippet, delete_knowledge_snippet), nor does it mention any prerequisites or exclusions.

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