get_awd_shipments

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

With no annotations, the description needed to disclose behavioral traits. It indicates read-only and stub nature but omits details on data refresh, pagination, rate limits, or that it supports time-range filtering (implied by parameters but not stated). This is insufficient for an agent to anticipate tool 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?

The description is concise, using a single sentence plus bracketed tags. It front-loads the purpose and stub note. However, the structure is slightly choppy with three separate segments; a more integrated sentence would improve flow.

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?

Given the tool has 7 optional parameters, no output schema, and many siblings, the description is too minimal. It doesn't explain the return value, how filtering works, or how it differs from related tools. This lack of completeness hinders the agent's ability to use it correctly.

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 100%, so baseline is 3. The description adds no additional meaning beyond the schema. Parameters like start_date and end_date are explained in the schema, but the description doesn't enhance understanding of their usage in the tool's context.

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 states 'AWD shipment tracking' with a '[read]' tag, clearly indicating it's a read operation for AWD shipments. However, it doesn't specify what specific tracking details are included, which could be more precise to differentiate from get_awd_inventory or get_awd_shipment_items.

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 only mentions it's a hosted endpoint and a stub for local use. It provides no guidance on when to use this tool over alternatives like get_awd_inventory or get_awd_shipment_items, leaving the agent without context for selection.

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