Create Foundry Entity

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

The description confirms it creates a new entity and returns the new UUID/document, consistent with openWorldHint=true and idempotentHint=false. However, it doesn't detail what happens to existing data, permission requirements, or failure modes beyond what annotations already imply. Minimal added context beyond the annotations.

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 concise sentences, front-loaded with the action, and no redundant information. Each word adds value, and it efficiently communicates purpose and return value.

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?

The schema and annotations handle many details, and the description states the return value. However, it lacks guidance on when to use this vs. sibling create tools, and it doesn't mention edge cases like override behavior or folder constraints, making it adequate but not complete.

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 100%, so the baseline is 3. The description only repeats 'raw Foundry document' in the body, which mirrors the schema's data parameter description. It adds no extra insight into folder, override, or userId semantics beyond what the schema already provides.

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?

Clearly states it creates a new Foundry entity with a raw Foundry document and lists supported types (Actor, Item, JournalEntry). The verb 'create' and resource 'Foundry entity' are specific, and it differentiates from siblings by focusing on raw document creation and returning a UUID.

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 entities, but offers no explicit comparison to alternatives like foundry_create_creature or foundry_update_entity. It provides no when-not guidance or exclusions, leaving the agent to infer when this raw-document approach is preferred over specialized creation tools.

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