upsert_trip

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

With no annotations, the description carries the full burden and does well: it discloses a mutation, an automatic whole-ledger re-validation, the return of updated ledger plus issues, and the crucial fact that the tool does not persist results itself (the user must save). Missing only details like permission requirements or failure behavior.

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?

Three short sentences, front-loading the core action before the side effect and return behavior. The instruction about handing the ledger back is actionable rather than filler, though it slightly overlaps the return-value statement.

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?

An output schema exists, so return values need not be explained (and the description partly repeats them anyway). For a mutation tool with no annotations and two fully undocumented nested object parameters, the description covers behavior and persistence but leaves the input contract 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% and both parameters are nested objects with additionalProperties allowed, so the description is the only source of shape information. It conveys only that 'trip' is one trip and 'ledger' is the whole ledger, giving no field-level semantics for either object.

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 gives a specific verb-resource pair (add or update one trip in the ledger) and states the side effect of re-checking the ledger, which separates it from the read-only sibling check_ledger. It does not explicitly name alternatives, but the core purpose is unambiguous.

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?

Usage is implied by 'Add or update one trip' and by the instruction to hand the ledger back for saving, so an agent can infer this is the write path. However, there is no explicit when-to-use guidance and no mention of when to prefer check_ledger or the other planning siblings.

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