remove_item

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

No annotations are provided, so the description bears full responsibility. It discloses the prerequisite ('no remaining references') but omits what happens if references exist (error? no-op?), whether removal is reversible, or any side effects (e.g., cascade deletions).

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 sentence, very concise. However, conciseness sacrifices necessary information, so it's not appropriately sized for the tool's complexity.

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?

With an output schema present, the description's job is reduced, but it still lacks essential behavioral context. For a tool with three required parameters and a conditional removal, more detail is needed about error states and side effects.

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%, and the description adds no meaning to parameters (scene_name, collection, item_id). It does not explain their roles or constraints beyond the schema's basic types and enum.

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 action ('remove') and the resource ('scene item'), and includes a condition ('when it has no remaining references'). It distinguishes from sibling tools like add_action or update_object. However, 'item' is not explicitly defined, though the schema's collection enum provides context.

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 on when to use this tool versus alternatives (e.g., update_* tools). The condition suggests a prerequisite for removal, but it doesn't advise on scenarios like error handling or when to choose this over other tools.

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