rhino_contour

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

The description indicates the tool generates new geometry, which aligns with the annotation 'readOnlyHint: false'. However, it does not disclose additional behavioral traits such as whether it modifies existing objects, requires specific document state, or side effects. The 'bridge required' hint is a constraint but not fully explained.

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 very short (one sentence) and front-loaded, but it omits crucial details that would justify its conciseness. Under-specification for a tool with multiple parameters and a nested schema.

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 having an output schema, the description does not mention what the tool returns. The input schema is complex with nested objects, but the description offers no guidance. The tool's purpose is stated, but the overall context is insufficient for correct invocation.

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 input schema has multiple parameters (doc_id, interval, direction, base_point, object_ids) with no documentation in the description. With schema description coverage at 0%, the description adds no meaning beyond the schema's basic types and titles.

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 action ('Generate') and the object ('equally spaced section curves'). It adds specificity with 'bridge required', which hints at a precondition. While it distinguishes from some sibling tools like rhino_section, the meaning of 'bridge required' is ambiguous without additional context.

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 provided on when to use this tool versus alternatives like rhino_section or rhino_section_at_axis. The description does not suggest any context, prerequisites, or exclusions.

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