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

Annotations already declare destructiveHint=true and openWorldHint=false, and the description's 'Safety' block largely restates those same facts rather than adding new information. It says nothing about whether the deletion is permanent or recoverable, whether it cascades to related records, or what happens when the id does not exist — the details an agent actually needs before invoking a destructive call.

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 short and front-loads the core action before the safety notes, so an agent gets the essential fact immediately. The safety block is somewhat boilerplate and partially redundant with the annotations, keeping it from a 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?

An output schema exists, so return values need not be explained, and the two-parameter schema is fully documented. However, for an irreversible delete the description omits permanence, cascade behavior, and error conditions, leaving meaningful gaps for a destructive tool.

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 coverage is 100%, so both trip_id and id are documented in the schema, establishing the baseline of 3. The description's 'by id' phrasing adds nothing about the required trip_id/id relationship or id format beyond what the schema already provides.

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 opens with a specific verb and resource ('Delete a Tripsy transportation by id'), which is unambiguous and matches the tool name. It is clearly distinguishable from siblings like tripsy_transportations_update or tripsy_transportations_show by the delete verb, though it never names those siblings explicitly.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites (e.g., ownership or collaborator permission needed to delete), and no note about confirming intent before calling. The only implied usage comes from the word 'Delete' in the first sentence.

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