itglue_create_document

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

No annotations are provided, so the description must convey safety and side effects. It only says 'Create a document' implying mutation, but does not disclose permissions, idempotency, or what happens on failure. No output schema, so return behavior is unclear.

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 extremely short (2 sentences), but this underspecification masks missing detail. It is not front-loaded with key behavioral info; it merely restates the obvious. True conciseness requires completeness.

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 no output schema and no annotations, the description fails to provide essential context like return value, validation behavior, or error handling. For a creation tool, the agent needs to know what to expect after invocation.

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 covers 67% of parameters, but the description adds no new insight beyond 'organizationId and name are required'. It does not explain semantics of restricted, public, or documentFolderId beyond their schema descriptions. No extra value.

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 verb 'Create' and resource 'document', distinguishing it from sibling tools like itglue_create_document_section and others targeting different entities. It could have explicitly noted the difference from document sections, but is still clear.

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 on when to use this tool vs alternatives. Prerequisites (e.g., organization must exist), error scenarios, or post-creation steps are not mentioned. The description only identifies required fields, which is already in the schema.

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