add_conn_to_crossing

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

With no annotations, the description carries full burden for behavioral disclosure. It states the action and return value, but does not discuss error handling, idempotency, or effects on existing connections. This is adequate for a simple add but lacks deeper edge-case transparency.

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 includes a formal Args block that largely duplicates schema descriptions and even lists a 'ctx' parameter not present in the schema. While organized, it could be more concise without losing key mode explanations.

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?

For a tool with three parameters and an output schema, the description covers single and batch usage, parameter roles, and return value. It does not mention edge cases or relationships to sibling tools, but overall it provides enough context 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?

Schema coverage is 100%, so baseline is 3. The description adds value by clarifying the mode-dependent semantics: which parameters are required for single items, and that 'items' overrides individual parameters. This goes beyond the schema's per-field descriptions.

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 opens with a specific verb+resource: 'Add a connection to a crossing point.' This clearly distinguishes it from sibling tools like add_connection and add_crossing_point, and the rest of the description reinforces the two operating modes.

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 explicitly explains when to use single vs batch mode, including that 'items' ignores individual parameters. However, it does not compare against alternatives like remove_conn_from_crossing or add_connection, leaving some usage context implicit.

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