media.character.lock

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that a Character Bible is created, but does not disclose whether the lock is permanent, whether it affects later media generation, whether it can be replaced, or what side effects it has. The word 'lock' suggests a possibly restrictive behavior that is never explained.

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 short sentence with no filler, so it is concise. However, it is under-specified rather than efficiently informative. The phrase 'Character Bible / identity continuity lock' is not structured to front-load the most actionable meaning.

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 no annotations, no output schema, and an input schema that lacks property definitions, this description is severely incomplete. It does not explain return values, side effects, required project context, or how the lock affects other media operations. An agent would struggle to know the expected effect or how to verify success.

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?

The description adds no meaning for the required parameters 'projectId', 'name', and 'description', and the input schema defines no properties despite requiring these fields. The parameter names are somewhat self-explanatory, but the description does not clarify format, constraints, or relationships between them. Because there are required parameters and zero schema-level property descriptions, the description should have compensated but did not.

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 uses a specific verb ('Create') and names a distinct resource ('Character Bible / identity continuity lock'). It is clear enough to be distinguished from sibling tools, none of which cover character identity management. However, 'identity continuity lock' is jargon and could be more explicit about what locking entails.

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 when-to-use or when-not-to-use guidance is provided. The description does not mention alternatives or prerequisites, and there is no explicit context for when an agent should call this tool versus other media creation tools. Usage is only vaguely implied by the phrase 'identity continuity lock'.

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