rhino_object_delete

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds minimal context ('from the document') beyond confirming deletion. Does not disclose undo behavior, batch effects, or impact on dependencies.

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?

Extremely concise (8 words, one sentence). No wasted words, but could be more informative without losing conciseness. Good for brevity, though depth is sacrificed.

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?

For a destructive tool with many siblings, the description is insufficient. It does not clarify what 'objects' refers to (geometry, blocks, etc.), whether undo is supported, or the scope of deletion. The output schema exists but is not used to compensate.

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%; the description provides no parameter information. The agent must rely solely on the schema, which has titles and types but lacks descriptions for object_ids. doc_id has a schema description, but overall the description adds no value for parameters.

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 'Delete' and the resource 'objects' in context 'from the document'. It is distinct from sibling tools like rhino_layer_delete or rhino_object_select, though it does not specify what types of objects are included.

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., rhino_boolean_difference, rhino_object_move_to_layer). No mention of prerequisites, irreversibility, or context where deletion is appropriate.

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