rhino_text

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

The description does add behavioral context beyond readOnlyHint=false by noting that Bridge mode honors the active dimension style and standalone mode uses a text-dot fallback. However, the undefined 'Bridge mode' terminology weakens the usefulness of this disclosure.

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 compact and front-loaded with the core action. The mode sentence is terse, though it introduces jargon that could confuse an agent.

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 large number of annotation-related siblings and the undefined mode terminology, the description is not sufficient for an agent to confidently choose and invoke this tool. The output schema helps, but the missing mode definition and lack of selection guidance leave clear 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 explain the meaning or usage of the key parameters such as text, location, height, layer, or name. Schema description coverage is very low, and the description provides little compensation beyond implying that text is placed at a 3D location.

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 opening phrase 'Add 3D text annotation' clearly states the verb and resource. The additional mode note adds context, though it does not explicitly differentiate this tool from siblings like rhino_text_dot or rhino_add_text.

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 is given about when to use this tool versus the many related annotation tools. The mention of 'Bridge mode' and 'standalone' implies a usage distinction, but these terms are not defined, so an agent cannot act on them.

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