rhino_export_gbxml

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

The description only says 'Export', implying a write operation. Annotations already set readOnlyHint=false, so no new behavioral information is added. There is no mention of file creation behavior, overwriting, or required permissions.

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, which is concise. However, it sacrifices necessary detail for brevity. It is front-loaded with the key action and format.

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 tool has multiple optional parameters and an output schema (though not described), the description is insufficient. It omits context about object selection ('object_ids') and zone naming ('zone_user_text_key'). An agent would need to infer usage from parameter names alone.

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 adds no information about parameters. Context indicates 0% schema description coverage, yet the description does not explain the purpose of path, doc_id, object_ids, or zone_user_text_key. The agent would have no additional guidance beyond the schema names.

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 states the specific output format (gbXML) and scope ('thermal/structural BIM payload'), differentiating it from other export tools like rhino_export_obj or rhino_export_ifc. The qualifier 'bridge only' adds specificity but is jargon that may confuse some agents.

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_export_ifc for IFC, rhino_export_obj for OBJ). The 'bridge only' hint is insufficient. The description does not mention prerequisites or exclusions.

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