create_document

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

With no annotations, the description must fully disclose behavioral traits. It only states 'Create a new document', implying a write operation, but omits details like idempotency, side effects, required permissions, or error behavior. This is insufficient for an agent to understand the implications of using the tool.

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 a single sentence, highly concise. However, given the nested parameter structure and lack of annotations, it may be too terse, sacrificing necessary detail. The front-loading is good (verb+object first), but the extreme brevity undermines 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, no annotations, and a nested input parameter with 0% schema coverage, the description is incomplete. It does not explain return values, required permissions, or how to properly construct the input object. The agent lacks critical context for correct 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 description coverage is 0%, yet the description adds no information about the input parameter or its sub-fields (name, content, collection_id). It does not clarify their meaning or usage, leaving the agent reliant solely on the schema, which lacks descriptions.

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 'Create a new document in Metabase' clearly specifies the verb (Create) and the resource (document), distinguishing it from sibling tools like create_card or create_dashboard. It unambiguously indicates this tool's role in creating a specific entity.

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 provides no guidance on when to use this tool versus alternatives or any preconditions. It fails to mention context such as required permissions, whether the user must have a parent collection, or how creation differs from other creation tools.

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