foundry_create_entity

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

The annotation readOnlyHint=false already indicates a mutation, and the description merely restates 'create' without adding extra behavioral details such as overwrite behavior, permission requirements, or effects on existing entities. It does not contradict annotations, but it also does not enrich them.

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, front-loaded sentence with no wasted words. It is efficient, but its extreme brevity borders on under-specification, so it does not quite earn a 5.

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 tool with 7 parameters, no output schema, and sparse annotations, a one-sentence description is grossly insufficient. It fails to explain the data format, valid entity types, folder/keepId/override semantics, or return behavior, leaving critical gaps for an agent to safely invoke it.

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 only 43% (3 of 7 parameters), and the description provides no parameter information at all. Parameters like folder, keepId, override, and entityType are left unexplained both in the schema and description, so the description fails to compensate for the low schema coverage.

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 resource (Foundry world entity), which is distinct from generic management tools. However, it does not differentiate among sibling create tools like foundry_create_scene or foundry_create_actor_embedded_documents, leaving ambiguity about what entity types are supported.

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 is provided on when to use this tool versus alternatives. The description is a single generic statement with no situational context, prerequisites, or exclusions, making it hard for an agent to decide between this and other create tools.

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