Create a knowledge base

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

The description adds the auth requirement 'Requires scope knowledge_bases:write', which is not visible in the annotations. Combined with annotations that already indicate this is a non-read, non-idempotent, non-destructive operation, the description provides sufficient behavioral context without contradicting the annotations.

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 two sentences, front-loading the tool's purpose before stating the required scope. Every sentence contributes useful information without repetition or filler.

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 create operation with five parameters, one required parameter, and no output schema, the combination of description, schema, and annotations covers the essential usage context. The missing piece is explicit guidance on when to create versus update, but the schema's parameter descriptions and the scope note make the tool usable.

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 description coverage is 80%, so the schema already documents most parameters meaningfully. The description's mention of 'facts and FAQs' loosely maps to basic_info and faqs, but it adds no parameter-level detail beyond what the schema provides.

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 uses the specific verb 'Create' with the resource 'knowledge base' and explains its purpose: storing facts and FAQs an agent can draw on during calls. This clearly distinguishes it from sibling tools like update_knowledge_base, delete_knowledge_base, list_knowledge_bases, and get_knowledge_base.

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 establishes that this tool is for creating a new knowledge base, but it does not explicitly say when to prefer it over update_knowledge_base or list_knowledge_bases. The scope requirement is helpful but does not guide an agent through the decision of when to create versus update.

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