foundry_create_actor_embedded_documents

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

The readOnlyHint=false annotation already signals a write operation. The description adds extra context about item creation using an upsert, revealing a non-obvious behavioral trait beyond the annotation. However, the upsert nuance is not fully elaborated, so it doesn't reach the highest level of transparency.

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?

Two sentences with the key action front-loaded. The second sentence adds a useful behavioral nuance but is slightly cryptic. Overall, it is appropriately concise without being under-specified.

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?

No output schema is present, and the description does not mention return values or prerequisites. The upsert behavior is mentioned but not fully explained, and the open-ended document schema is a significant gap for a create operation. The tool has moderate complexity, so more guidance would improve completeness.

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?

The schema provides descriptions for 60% of parameters (actorUuid, userId, clientId) and the documentType enum explains itself. The tool description clarifies that documents are for Items or ActiveEffects, but it does not compensate for the vague 'JSON object accepted by Foundry' description of the documents array, nor does it provide examples or structure.

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 uses a specific verb 'Add' and names the resource ('Items or ActiveEffects') and target ('one actor'), clearly distinguishing this from the update and delete sibling tools. It is unambiguous about what the tool does.

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 through 'Add' and the tool name, but does not explicitly state when to use this versus update/delete or provide alternative guidance. The phrase 'uses the relay's supported Actor items upsert' hints at behavior but not at selection criteria.

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