doc_create

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

With no annotations, the description carries the behavioral disclosure burden. It usefully reveals that the default doc_id is the hash of the initial content and that the document is editable, adding value beyond a bare 'create' statement. However, it omits other behavioral aspects such as how visibility, tags, or base64 content are handled.

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 tight sentence with no filler. It front-loads the action ('Cria um documento editável') and adds the most important behavioral detail about doc_id afterward.

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, 0% schema coverage, and no annotations, this description is too sparse to fully support correct invocation. It covers the creation intent and doc_id default, but lacks guidance on required inputs, parameter relationships, and usage boundaries among the many document sibling tools.

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 0%, so the description needs to compensate. It provides meaningful semantics for doc_id ('default is the hash of the initial content'), but leaves the other seven parameters—title, content, mime, tags, visibility, agent_id, content_base64—unexplained.

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 states a clear action and resource: 'Cria um documento editável' (creates an editable document), giving a specific verb and object. It is clearly a creation tool, though it does not explicitly distinguish itself from siblings like doc_put or doc_fork.

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?

There is no guidance on when to use this tool versus alternatives. The hint 'compartilhe esse id' (share this id) implies a follow-up action but does not clarify when doc_create should be preferred over doc_put, doc_update, or other document tools.

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