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

Beyond annotations (readOnlyHint=false, destructiveHint=false), it describes the parsing/geocoding behavior, the example, and the ability to repair one or all transport items. It doesn't discuss failure modes or geocoding dependencies, but annotations already signal a mutating, non-destructive repair operation.

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 two sentences with a concrete example and no filler. Key information is front-loaded, making it easily scannable.

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 repair tool with 5 optional parameters and no output schema, the description covers the main behavior, scope, and parsing/geocoding mechanism. It doesn't specify behavior when no parameters are supplied or if both itemId and tripId are provided, but the schema covers parameter semantics sufficiently.

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 100%, so the baseline is 3; the description reinforces that itemId selects a single item and tripId selects all transport items, and the example clarifies how names are parsed. It adds minimal parameter-level detail beyond the schema.

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 names a specific action ('repair'), a specific resource ('transport/flight items missing origin coordinates'), and the mechanism (parse item name + geocode). It gives a concrete example and states scope (single item or all in trip), which distinguishes it from generic trip_item_update or trip_transport_add.

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?

It clearly specifies the intended use case: items missing origin coordinates that need parsing/geocoding, and mentions both single-item and trip-wide repair. It doesn't explicitly name alternative tools or exclusion conditions, but the context is unmistakable.

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