remove_conn_from_crossing

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

With no annotations provided, the description is expected to disclose side effects, but it only says the connection is removed and a confirmation message is returned. It does not explain whether the connection is deleted, what happens to related data, or whether errors occur if the crossing point or connection does not exist.

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 short but redundant: the first sentence 'Remove a connection from a crossing point.' and the second sentence 'This tool removes a connection from a crossing point...' say essentially the same thing. The docstring-style Args/Returns section is useful but adds little new information.

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 simplicity of the tool (two string parameters, no nested objects), the description provides a basic explanation of the operation and return value. However, it omits edge cases, side effects, and contextual usage relative to sibling tools, so it is only minimally complete.

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 already covers both parameters with identical descriptions, giving 100% schema coverage. The description adds no additional meaning beyond what the schema provides, and it also mentions a `ctx` parameter that is not part of the schema, which could be confusing.

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 'Remove a connection from a crossing point' and repeats the action with the resource named in the tool name. It is specific and semantically distinct from the sibling `add_conn_to_crossing` since removal is the inverse operation.

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 no guidance on when to use this tool versus alternatives such as `delete_crossing_point` or `update_crossing_point`. There is no mention of prerequisites, exclusions, or which scenarios call for this tool.

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