geom_line_intersection

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the domain and category but fails to describe critical behaviors: what happens if lines are parallel (no intersection), the format of the output (e.g., coordinates), error handling, or computational assumptions. This leaves significant gaps for a tool with two complex input parameters.

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 concise and front-loaded, stating the core purpose in the first phrase. The additional context ('Domain: geometry, Category: general') is brief but relevant. There is no wasted text, though it could be more structured (e.g., separating usage notes).

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 complexity (two nested object parameters, no schema descriptions, no output schema, no annotations), the description is incomplete. It lacks details on parameter formats, output structure, error conditions, and mathematical assumptions. While concise, it does not compensate for the missing structured information, making it insufficient for reliable tool 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 0% description coverage, with two nested object parameters ('line1', 'line2') completely undocumented. The description does not add any parameter semantics—it does not explain what constitutes a 'line' (e.g., two points, slope-intercept form) or the expected structure. This is inadequate for a tool with complex, undefined inputs.

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's purpose: 'Find intersection point of two lines in 2D space.' It specifies the verb ('Find'), resource ('intersection point'), and domain ('2D space'), making it easy to understand. However, it does not differentiate from sibling tools like 'geom_segment_intersection' or 'geom_circle_intersection', which prevents a perfect score.

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 provides minimal usage context by mentioning 'Domain: geometry, Category: general,' but it does not explicitly state when to use this tool versus alternatives (e.g., for lines vs. segments or circles). No guidance on prerequisites, edge cases (e.g., parallel lines), or alternatives is given, leaving the agent with insufficient direction.

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