Crear Mundo

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

With no annotations provided, the description carries the full burden for behavioral transparency. It says 'Crea' and 'Registra', but it gives no concrete details about persistence, side effects, authorization, or whether the change is reversible.

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 short but under-specified. The second sentence 'Registra el módulo visible en la app' is unclear and does not earn its place because it does not clarify the tool's behavior enough to assist an agent.

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?

Even though an output schema is present, the description lacks any context about project relationships, required parameter formats, or intended selection. The description is too thin to be complete for a tool with three input fields and no annotations.

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 input schema has 0% description coverage, and the description does not explain 'proyecto', 'nombre', or 'descripcion'. It does not add meaning beyond the raw parameter names, so the agent cannot confidently construct valid arguments.

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 begins with 'Crea un mundo', a specific verb and resource, and the parenthetical 'Mundos -> ficha' anchors it to the app's domain. It is distinct from sibling tools like 'escribir_guion' or 'restaurar_snapshot', though the trailing clause about 'módulo visible' adds ambiguity.

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?

There is no guidance on when to use this tool, when not to use it, or how it relates to siblings such as 'proyecto' or snapshot tools. The agent is left to infer from the name alone.

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