delete_entities

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

Beyond the annotations (destructiveHint, idempotentHint), the description adds crucial behavioral details: deletion is permanent and not undoable, includes all descendants, excludes the scene root, and returns { deleted: <count> }. This meaningfully exceeds what annotations provide and gives an agent a clear mental model of the tool's behavior.

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: the primary action comes first, followed by important warnings, return value, and usage alternatives. Every sentence contributes meaningful information with no repetition or filler.

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?

The tool is simple (one parameter), and the description covers the essential aspects: destructive permanence, descendant deletion, the scene root limitation, return value, and when not to use it. The annotations cover idempotency and destructiveness, so no critical context is missing.

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?

With only one parameter and 0% schema description coverage, the description helps by clarifying that the ids refer to entities to be deleted along with their descendants, and that the scene root cannot be deleted. While the schema indicates UUID format, the description adds semantic constraints not present in the schema.

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 clearly states the tool's action and scope: 'Permanently delete entities and all of their descendants.' It also distinguishes itself from related tools by explicitly naming alternatives like modify_entities and remove_components, making it easy for an agent to identify when this tool is the right choice.

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?

The description provides explicit 'When NOT to use' guidance with specific alternatives: hiding an entity should use modify_entities, and removing a single component should use remove_components. It also conveys the destructive, permanent nature and the special restriction that the scene root cannot be deleted.

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