Create doc

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

Annotations are all false, so the description must disclose behavioral traits. It only states 'Create', indicating a write operation, but omits details like idempotency, side effects, or required permissions. Minimal behavioral insight provided.

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 concise—one sentence plus a brief note. It front-loads the main purpose without unnecessary words. While it could be more informative, it is efficient and to the point.

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 8 parameters, no output schema, and complex metadata, the description is insufficient. It lacks details on return values, creation behavior, error conditions, and idempotency, leaving gaps for an AI agent to invoke 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 baseline is 3. The description mentions doc type examples, which are already in the schema's doc_type description. It adds no additional meaning beyond what's already documented.

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 explicitly states the verb 'Create' and the resource 'durable doc' with concrete examples (spec, runbook, ADR, RFC). It distinguishes from sibling tools like memory_update_doc and memory_create_task by specifying the action and resource type.

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 implies usage ('Create a durable doc') but provides no explicit guidance on when to use this tool versus alternatives or context about prerequisites. The note about the same handler adds minimal direction.

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