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

The description opens with 'MUTATES KnowledgeOwl data' and specifies the HTTP method, which reinforces the destructiveHint annotation. It also discloses that the tool returns the created snippet, adding value beyond the annotations by describing the operation's effect and response.

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?

Three focused sentences with no wasted words. The mutation warning and endpoint are front-loaded, followed by the key parameter guidance and return behavior — every sentence earns its place.

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?

For a creation tool, the description plus schema covers required parameters, the general behavior, and the return value. It does not describe error cases or prerequisites like authentication, but the annotations and schema provide enough context for an agent to invoke this tool correctly.

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 schema already documents all three parameters. The description adds valuable meaning by explaining that the snippet body/content should be passed via the fields parameter, with a snippet-specific example ('snippet_text/body'), which helps an agent populate the nested object correctly.

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 names a specific verb ('creates'), a specific resource ('reusable content snippet'), and the exact KnowledgeOwl endpoint (POST /snippet.json). This clearly distinguishes it from sibling tools like create_article, create_category, and create_glossary_term.

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 through the verb 'creates' and the resource type, but there is no explicit guidance about when to prefer this over alternatives, or when a different tool (e.g., update_snippet/list_snippets) would be more appropriate. No exclusions or conditional routing are provided.

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