cleanup_scene

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

Annotations already declare destructiveHint=true, and the description adds that it cleans orphan datablocks and normalizes names, giving some behavioral context. However, it does not disclose what happens to objects, whether normalization is reversible, or how the 'purge_unused' parameter affects behavior. The description aligns with annotations (no contradiction).

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 that front-loads the primary purpose. Every word contributes to stating the core actions, making it highly concise and structured.

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?

Despite annotations and output schema existing, the description is too vague for a destructive tool. It omits parameter semantics, the exact scope of 'orphan datablocks', and what 'normalize names' entails. An agent would not know the full side effects or prerequisites, making the description incomplete.

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 description coverage is 0% for the single 'purge_unused' parameter, so the description must compensate. It only implies the parameter's effect through 'clean orphan datablocks' but never explicitly explains what 'purge_unused' controls or its default behavior. Insufficient for an agent to understand the parameter.

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 identifies the action ('clean' and 'normalize') and resource ('datablock', 'nama'), conveying the tool's main purpose. However, it is written in Indonesian and does not differentiate from sibling tool 'purge_orphans', which likely overlaps in functionality.

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 guidance is provided on when to use this tool versus alternatives like 'purge_orphans' or other cleanup tools. There are no exclusions, prerequisites, or contextual hints for selecting this tool.

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