rhino_section

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

The description indicates a mutation ('Slice') consistent with readOnlyHint=false, but provides no additional behavioral details such as whether objects are altered or new objects are created.

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 extremely concise with a single sentence and a parenthetical note. Every word serves a purpose with no redundancy.

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?

Despite the output schema being present, the description lacks coverage of all parameters (e.g., doc_id) and does not explain the tool's behavior in sufficient depth for a nested 4-parameter tool.

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% and the description adds no parameter-level guidance. It mentions 'listed objects' and 'plane' but omits doc_id and does not clarify the role of plane_origin and plane_normal beyond the schema.

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 tool slices objects with a plane using a specific verb and resource. However, it does not specify the output (e.g., section curves) or distinguish from similar tools like rhino_section_at_axis.

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 mentions 'bridge required' as a dependency but offers no guidance on when to use this tool versus alternatives like rhino_contour or rhino_section_at_axis.

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