foundry_create_canvas_documents

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

The description is consistent with the annotation readOnlyHint=false (it's a create/write operation). However, it provides no additional behavioral context such as permissions required, side effects, idempotency, or return value. The simple 'create' action is clear, but lacks depth beyond what annotations already signal.

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, focused sentence that immediately communicates the core purpose. It is efficiently written with no filler or repetition, fitting the tool's straightforward nature.

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?

For a create tool with no output schema, the description is minimal. It doesn't explain what the return value will be, any preconditions, or how the created documents manifest. However, the operation is conceptually simple, and the schema covers required parameters, so this is a borderline pass but with clear gaps.

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 coverage is 80%, with most parameters having descriptions. The description adds no parameter-level detail beyond stating 'one or more', which is already reflected in the 'data' property's description. Since the schema handles the semantics, the description doesn't add significant value, but it doesn't need to.

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 action ('Create') and the resource ('canvas embedded documents'), which distinguishes it from the sibling tool 'foundry_create_actor_embedded_documents'. The phrase 'one or more' also communicates the tool's multi-create capability, making the purpose unambiguous.

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 for creating canvas documents, and the name differentiates it from actor-embedded document creation. However, there is no explicit guidance on when to prefer this tool over alternatives, nor any mention of prerequisites or exclusion criteria. Usage context is only implied by the resource type.

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