kaiten_create_document

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

With no annotations provided, the description carries the behavioral burden. It usefully discloses that text content is auto-converted and data content is raw ProseMirror JSON. It does not disclose success/error behavior, whether text and data are mutually exclusive, or any permission requirements, leaving notable gaps for a mutation tool.

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?

Two short, front-loaded sentences state the operation and the key content-format decision without filler. 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?

The rich input schema covers parameter details, but without annotations or an output schema the description leaves important context unstated: what a successful create returns, how the API behaves on invalid input, and whether text and data can be combined. Adequate for a straightforward create call, but not fully complete.

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%, putting the baseline at 3. The description adds value by framing text and data as alternative content paths ('use text ... or data ...'), clarifying the relationship between the two main parameters beyond what each individual schema description states.

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) and the resource (a new Kaiten document), so an agent can identify the operation. It does not explicitly distinguish this from sibling document tools like kaiten_update_document or kaiten_create_document_group, but the verb and resource make the purpose unambiguous.

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 offers useful input-format guidance ('text' for markdown vs 'data' for raw ProseMirror JSON), which helps with parameter selection. It does not, however, say when to choose this tool over alternatives, nor does it mention prerequisites such as needing a parent_entity_uid; the creation use case is implied rather than explicitly contrasted with other tools.

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