documents_create

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

With no annotations present, the description fails to disclose behavioral traits such as persistence, permissions required, or result of the operation. It only repeats the basic action without details on side effects or 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?

The description is one short sentence, immediately front-loading the action and format. No extraneous words.

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?

Considering 7 parameters, no output schema, and no annotations, the description is too sparse. It omits mention of required collectionId, optional flags like publish/template, and nesting via parentDocumentId, leaving the agent without enough context to select or invoke the tool appropriately.

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?

The schema already describes all parameters at 100% coverage. The description adds no new parameter semantics; the phrase 'Provide title and text in Markdown' is redundant with the schema and misleads by implying text is required, though it is optional (only title and collectionId are required).

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 tool's function with a specific verb ('Create') and resource ('a new document'), and additionally specifies content format ('text in Markdown'). This distinguishes it from update/delete/import operations.

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?

No guidance is provided on when to use this tool versus alternatives such as documents_update, documents_import, or documents_copy. The description doesn't mention exclusions, prerequisites, or alternative tools.

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