list_my_transports

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

No annotations, but description mentions ordering ('newest first'), optional filtering, and that entries include 'live progress'. Lacks rate limits or pagination details, but sufficient for a read-only listing.

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 concise sentences covering function, filter, and use cases. No redundant words.

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 one optional parameter and no output schema, description explains what it does and why to use it. Missing return field details, but 'live progress' gives enough context.

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% (status parameter fully described). Description adds 'optionally' and lists enum values, which repeats schema. No additional meaning beyond 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?

Clearly states 'List your own transports (newest first)' with specific verb and resource. Distinguishes from siblings like 'get_transport_status' (single transport) and 'get_pending_transports' (only pending).

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?

Provides explicit use cases: 'monitor your shipments' and 'recover a transport jobId'. Does not contrast with alternatives, but the use case is clear.

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