apply_track_road_edit

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

Annotations already mark this as destructive and non-read-only, so the description does not need to restate that. It adds a small amount of context with 'exact' and 'after separate host confirmation,' but it does not disclose what will be modified, whether the change is reversible, or what happens on failure. For a destructive tool, this is insufficient behavioral 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 is a single sentence with no filler. It front-loads the action and adds a condition, making it efficient. However, the extreme brevity sacrifices useful detail, so it earns a 4 rather than 5.

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 that this is a destructive, write-oriented tool with four parameters (three required) and no parameter descriptions, a one-sentence cryptic description is not complete enough for an agent to invoke it safely. The output schema may cover return values, but the surrounding workflow, parameter semantics, and destructive impact remain unexplained.

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 0%, so the description must compensate for the undocumented parameters. It weakly aligns with 'proposal_digest' and 'confirm,' but 'proposal_id' and the optional 'changeset_id' receive no explanation, and there is no guidance on how the parameters relate or why 'confirm' is required.

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 states a verb ('Apply') and a target ('an exact dev-API digest'), and the tool name adds 'track road edit' context. However, it is jargon-heavy and does not clearly explain what the tool actually does to a track road edit, nor does it distinguish itself from siblings like preview_track_road_edit or apply_osm_edit.

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 phrase 'after separate host confirmation' provides a weak usage condition, implying the tool should be run only after an external confirmation step. But there is no explicit guidance about when to use this tool versus alternatives, no prerequisites, and no warning about when not to use it.

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