rhino_panel_curvature_classify

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

Annotations state readOnlyHint=true; description adds that standalone uses a heuristic (no full Gaussian K) and bridge reports true curvature, providing useful behavioral context beyond annotations.

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 sentences with main action front-loaded. Modes are presented in a separate line. Efficient but could integrate mode descriptions more smoothly.

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?

Description covers main action and modes but omits parameter details and return value structure. For a tool with output schema and 0% schema coverage, the description is incomplete.

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% (top-level args property undocumented). Description does not explain any of the six nested parameters (doc_id, count_u, count_v, etc.), leaving the agent without guidance on their meaning or expected values.

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?

Description clearly states verb 'Classify' and resource 'UxV panel by curvature class' with explicit class names. Does not differentiate among sibling tools like rhino_panel_planarity.

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?

Distinguishes between standalone and bridge modes, implying when each is appropriate, but no explicit when-not-to-use or comparison with alternatives.

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