rhino_bim_metadata_set

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

Beyond the readOnlyHint=false annotation, it discloses what is written (Pset_RhinoMcp::<key> user_text), where (each object; additionally Rhino's IFC property-set table in bridge mode), and the downstream effect (IFC export). It doesn't state whether existing metadata is overwritten or whether the operation is reversible, but the core mutation behavior is transparent.

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?

Two short paragraphs with the main action front-loaded and a technical mechanism in backticks; no filler or redundant restatement of the tool name.

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 description covers mode-dependent behavior and export relevance, but with no schema descriptions counted and no guidance on required args, overwrite behavior, or relationship to rhino_bim_pset_* tools, an agent could select it yet still struggle to populate args correctly. The output schema reduces the need to explain return values, so the remaining gap is invocation semantics.

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?

Context indicates 0% schema description coverage, and the description does not name required parameters like object_ids or entity_type nor explain doc_id, pset_name, or properties mechanics. It offers only conceptual grounding ('IFC entity + property-set metadata') and the default Pset_RhinoMcp key prefix, which is not enough to invoke the nested args confidently.

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?

Opening sentence names a specific action ('Tag objects') and a specific resource ('IFC entity + property-set metadata'), and the rest details the write mechanism (user_text keyed as Pset_RhinoMcp::<key>) plus bridge-mode behavior, which separates it from generic BIM pset tools in the sibling list.

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 implies the main use case—attaching BIM metadata before an IFC export—and explains standalone vs bridge behavior, but it never explicitly states when to choose this over rhino_bim_pset_set/get/delete or rhino_export_ifc. There are no exclusions or alternative tool names.

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