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

Annotations already indicate it's not read-only, not destructive, not idempotent, and not open-world. The description adds relevant behavioral context: 'roles are live immediately' and the effect of seedPanels on panel creation, plus the interaction with import_brief. This goes beyond annotations, though it doesn't cover error conditions or permissions.

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 concise and front-loaded with the main action and key details. It uses parentheses for examples efficiently. However, the sentence about seedPanels is somewhat convoluted ('Omit seedPanels:false'), which could be clearer.

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 10 parameters, only 3 required, and low schema coverage, the description provides some critical context but leaves gaps. It doesn't explain projectId or type beyond mc_template, and doesn't mention that the entry is created within a world/project. Given no output schema, it should clarify what's returned. Partially 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 very low (10%), with only seedPanels having a description in the schema. The description compensates by explaining seedPanels behavior ('seedPanels:false' and defaults) and mentioning mc_template as a special type. It adds meaning beyond the schema for these key parameters, but doesn't cover other parameters like tags or description. Baseline 4 when zero params? But here 10 params, coverage 10%, description compensates partially, so 4.

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 the action: 'Create a world bible entry' with examples (character, location, lore). It adds value by mentioning default panels pre-created. However, it doesn't explicitly differentiate from create_world or other creation tools, leaving some ambiguity about the scope of 'entry' vs 'world'.

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?

It provides some conditional guidance: 'mc_template creates a player role' and 'Omit seedPanels:false if you plan to import_brief the panels separately.' This implies usage of mc_template and when to disable seedPanels, but lacks general when-to-use vs alternatives like update_entry or create_world.

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