rhino_bim_pset_delete

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

The description adds minimal behavioral context beyond the annotation `destructiveHint: true`. It does not clarify whether the PropertySet itself is removed or just its properties, nor does it address reversibility, undo, or side effects. The ambiguity reduces usefulness for safe invocation.

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, well-structured sentence that conveys the core purpose without extraneous words. It is front-loaded and every word contributes meaning.

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?

Given the presence of an output schema and descriptive parameter properties, the description is nearly complete. However, it omits important context for a destructive operation, such as confirmation behavior or impact on related data, leaving minor gaps.

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?

The description does not add parameter-level meaning, but the input schema provides full descriptions for doc_id, object_id, and pset_name (100% coverage). Since the schema already handles parameter semantics, the description's lack of additional detail is acceptable.

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), the resource (every property under a named PropertySet), and the target (an object). It effectively differentiates from sibling tools like rhino_bim_pset_get and rhino_bim_pset_set, which are get/set operations.

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 lacks explicit guidance on when to use this tool versus alternatives, such as when to delete a PropertySet versus using get or set. No usage context or preconditions are provided, leaving the agent to infer based solely on the action name.

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