list_deliveries

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

With no annotations, the description must carry the safety burden itself. 'List' implies a read-only operation and the fields describe what is returned, but the description does not explicitly confirm it has no side effects, nor does it mention optional filtering behavior or output characteristics.

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?

A single front-loaded sentence contains the core action, scope, and return fields with no filler or redundant wording.

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?

For a simple 2-parameter list operation, this is minimally sufficient: an agent knows the date is required and what fields are returned. However, it leaves the optional status filter unexplained and provides no reassurance about read-only behavior, pagination, or empty results.

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?

Only 50% of parameters carry schema descriptions, and the description does not compensate: the required 'date' is repeated but the optional 'status' parameter is not described beyond its enum values. No explanation of status as a filter is provided.

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 names a specific verb ('List'), a resource ('deliveries'), a scoping condition ('for a date'), and the returned fields (weight, address, time window). This clearly distinguishes it from siblings like list_vehicles or plan_routes.

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 date condition implies this is for fetching a delivery manifest for a specific day, but there is no explicit statement of when to prefer it over siblings such as get_route_detail or export_route_sheet. No alternatives or exclusions are given.

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