Add a document

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

The description discloses the write nature (matching readOnlyHint=false) and adds specific failure modes, going beyond the annotations to explain behavior.

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 concise, using two sentences that cover purpose and key constraints without unnecessary details.

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 simple create operation, the description covers necessary context: what it does, when it fails, and the need for user confirmation. No output schema is required for this tool.

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 covers 'body' and 'slug' descriptions, but 'title' and 'tags' lack descriptions. The description text adds no parameter-specific information, so it does not compensate for the missing schema coverage.

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 ('Create a new markdown document') and the resource ('knowledge base'), distinguishing it from sibling tools like kb.search and kb.get.

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?

Explicitly states failure conditions (writes disabled, slug already exists) and instructs the user to ask before calling, providing clear guidance on when to use the tool.

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