Point: Intersection (deterministic)

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

Adds value beyond readOnlyHint by describing the handling of multiple candidates via ref_x/ref_y and the return format {x, y}. However, missing mention of behavior when no intersection exists.

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 concise sentences plus a note on return, front-loaded with key functionality, 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?

Covers main functionality and return, but lacks details on edge cases like parallel or non-intersecting entities. Output schema likely fills some 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?

Schema description coverage is 100%, and the description reinforces the purpose of ref_x/ref_y as selecting nearest candidate. Adds context by linking parameters to entity types.

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 'compute' and resource 'intersection', specifies supported entity types (LINE-LINE, LINE-CIRCLE, CIRCLE-CIRCLE), and distinguishes from sibling tools like point_from_snap and point_tangent.

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?

Implicitly indicates use for geometric intersections, but lacks explicit guidance on when to use versus alternatives such as point_from_snap for snapping to intersections.

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