get_transport_status

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

With no annotations provided, the description carries full burden. It discloses public access, and adds a secondary behavioral signal: 'a delivered shipment also bumps the target cell resource balance'. It does not explicitly state read-only nature, but the context implies idempotent query.

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, each serving a distinct purpose: main function and unique differentiation + secondary effect. No redundant phrases. Slightly dense but efficient.

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?

No output schema exists, but the description lists the returned data fields (lifecycle status, interpolated position, hops traveled, ETA/arrival) and a secondary effect, providing adequate context for an agent to understand what the tool returns.

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% for the single parameter 'jobId', so baseline is 3. The description adds context by referencing the source of jobId ('from transport or list_my_transports'), but this largely restates the schema description. Marginal additional value.

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 clearly states the verb 'Get' and the resource 'live status of one transport by its jobId', listing specific data elements (lifecycle status, position, hops, ETA). It explicitly distinguishes itself from siblings by stating 'This is the only source of a shipment live progress; the world map never carries shipments.'

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?

The description explicitly states 'Public — works for any jobId', indicating it can be used for any transport without authentication. It also implies when not to use alternatives by noting the world map lacks shipment data, but does not explicitly mention other sibling tools for related but distinct purposes.

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