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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's "Read-only" is reinforcement rather than new information. The real added value is the disclosure of the response's breadth — audit history, documents, stops, weighings — which tells the agent to expect a heavy payload. It does not mention size limits, pagination, or behavior when the trip is missing, which keeps it below 5.

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?

Two sentences, both front-loaded: the payload contents first, then the read-only/usage note. Every clause adds information — the enumeration is dense but each item is a distinct returned section, not filler.

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?

With no output schema, the description must convey what comes back, and it does so thoroughly, including secondary data like audit history and weighing records. The remaining gap is operational: no guidance on payload size, error behavior for an unknown trip_id, or ID format for the single parameter.

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?

There is a single required parameter, trip_id, with 0% schema description coverage, so the description carries the burden. "Read one trip" implies trip_id identifies the trip, but it never states whether it is an internal ID, a trip number, or a UUID, nor what happens on an invalid value. Adequate but with a clear gap.

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?

States a specific verb and resource ("Read one trip in full") and then enumerates exactly what "in full" covers: fields, crew and route, weights and TTN, documents, status-transition history, field-level change audit, route stops and weighing records. This clearly separates it from the list/update/create siblings without needing to name them.

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?

Gives an explicit when-to-use rule: "Use before changing a trip so you quote its real current state." That is a concrete workflow trigger rather than vague context. It stops short of naming the alternative read paths (e.g. list tools) or stating when not to use it, so it is not a full 5.

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