Delete World Model Persona

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds no additional behavioral context, such as whether the deletion is permanent, what associated data is affected, or how missing IDs are handled. It merely restates the action.

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 concise sentence with no filler or repetition. It conveys the essential action and target efficiently.

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?

While the tool is simple and annotations provide safety cues, the description omits return-value behavior and edge-case handling (e.g., what happens if the persona or world model does not exist). Without an output schema, this information would be valuable but is not critical for a straightforward deletion.

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?

Input schema documentation covers both parameters (persona_id, world_model_id) with descriptions, achieving 100% schema description coverage. The tool description does not add any extra parameter meaning, so the baseline of 3 is appropriate.

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 'Delete a persona from a world model' clearly states the action (delete) and the specific resource (persona within a world model). It distinguishes this tool from sibling tools like lyzr_world_model_delete (which removes an entire world model) and lyzr_world_model_delete_test_case/scenario.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives (e.g., when to delete a persona versus deleting the entire world model), nor does it state any prerequisites or edge cases such as whether the world model must exist.

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