apply_osm_edit

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

Annotations already indicate that this is destructive and not read-only, and the description adds a useful workflow safeguard ('reviewed proposal', 'client-host confirmation'). However, it does not disclose what gets modified or destroyed, what happens on application, or any safety considerations beyond what the annotations imply. The description is consistent with annotations, so no contradiction.

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, front-loaded sentence with no filler or repetition. It states the core action first and then the key precondition, which is an efficient structure for an agent to parse quickly.

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 destructive mutation tool with two required parameters and no parameter-level documentation, this description is too sparse. It omits how the proposal_digest should be used, what the changeset_id does, and what outcome the agent should expect after applying. The output schema and annotations help, but they do not fill the gap left by the absent parameter semantics.

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%, and the description provides no explanation of proposal_id, proposal_digest, or changeset_id, nor how they relate to the review/confirmation workflow. The description does not compensate for the missing schema parameter documentation at all, leaving an agent to guess the meaning and provenance of required arguments.

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 uses a specific verb ('Apply') and a clear resource ('a reviewed proposal'), so an agent can tell this is the mutation step in an OSM editing workflow. It does not explicitly differentiate from sibling tools like verify_osm_edit or apply_track_road_edit, but 'proposal' narrows the scope enough to avoid major ambiguity.

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 a separate client-host confirmation' establishes a clear prerequisite and workflow context: this tool should only be called once confirmation has happened. It does not mention alternatives or when not to use it, but the conditional context is explicit enough for most invocation decisions.

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