create_document

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Create a document' and mentions publishing requirements, but fails to explain what happens when neither collection_id nor parent_document_id is provided (e.g., draft creation, failure). No details on permissions, side effects, or final state are given.

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 short (two sentences), but the first sentence ('Create a document') is largely redundant with the tool name. The second sentence adds value about publishing requirements. While concise, the structure is not front-loaded with the most critical information; an improved version would move key constraints first.

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 the complexity (7 parameters, no output schema, no annotations), the description is insufficient. It does not explain return values, required prerequisites beyond publishing, error states, or the effect of omitting optional parameters. The tool's behavior in the common case (draft creation) is entirely absent.

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%, meaning the schema provides no parameter documentation. The description must compensate but does not: it only references collection and parent in the context of publishing, and does not explain the purpose or expected values of parameters like icon, text, template_id, or publish. This leaves agents guessing about parameter semantics.

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 creates a document, which is a specific verb+resource. It distinguishes from sibling tools like create_comment because the resource (document vs comment) is explicit. However, it does not elaborate further to differentiate from other document-related tools like update_document or list_documents.

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 by mentioning publishing requirements, but it does not explicitly state when to use this tool versus alternatives like create_comment or update_document. No exclusions or context for non-publish scenarios are provided.

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