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

Annotations already mark readOnlyHint=false, so mutation is expected. The description goes further by disclosing the folder ID-vs-NAME wire convention, that unknown item types are rejected, and that system data is deep-merged with Foundry defaults. These are useful behavioral details beyond the annotation booleans.

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 tight, front-loaded with the key sibling distinction, and each sentence earns its place by adding operational detail rather than restating schema fields.

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 a nested system object and no output schema, it covers required parameters, type constraints, folder handling, and a reference for the system blob shape. It could detail the full return payload beyond the folder name convention, but the guidance is sufficient 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 coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying the folder response convention, enumerating valid type values for D&D 5e, and pointing to world-item-get for the canonical system data shape.

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?

States the action ('Create'), the resource ('the world's Items Directory (game.items)'), and immediately differentiates from the sibling item-create, which adds to an actor's inventory. This removes any ambiguity about what the tool targets.

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?

Explicitly names the alternative tool (item-create) and gives the selection condition: use this for shared loot, master copies, or items independent of any actor. It also provides a practical pointer to folder-list for discovering folder IDs.

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