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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent creation, so the description's job is additive. It does that by disclosing that default panels are created automatically (default true) and by explaining the live role semantics — a role with a matching character name is that person, one without is a player variant. It does not mention error modes, dedup behavior on repeat names, or permission needs.

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 main action is front-loaded, but the middle is dense nested-parenthetical prose about role/character name identity that takes effort to parse. Every sentence is relevant, yet the phrasing is not economical.

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 10-parameter creation tool with no output schema and no annotation coverage of side effects, the description covers the two trickiest behaviors (panel seeding, role semantics) but leaves most field semantics and the returned identity unaddressed. Adequate but with clear gaps.

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 only 10% across 10 parameters. The description adds meaning only for `type` (mc_template role semantics) and `seedPanels` (default true, interaction with import_brief); `name`, `tags`, `series`, `aliases`, `tagline`, `avatarUrl`, `projectId` and `description` are left entirely to bare schema types. That is far short of compensating for the coverage gap.

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?

Opens with a specific verb+resource ("Create a world bible entry") and enumerates the kind of entities covered, so an agent can distinguish it from update_entry or delete_entry at a glance. It stops short of explicitly contrasting itself with those siblings, but the action and object are unambiguous.

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?

Gives real conditional guidance: omit seedPanels:false when you intend to import_brief the panels separately, and explains the mc_template path versus normal entry creation. It lacks exclusions like "use update_entry to modify an existing entry," which keeps it from a 5.

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