deliveries_retrieve__get_customer_deliveries

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

Annotations already mark this as read-only/non-destructive. The description adds valuable behavior beyond annotations: dates are in local terminal time, data availability is guaranteed for 7 days, the tool is a wrapper consuming underlying API quota, and caching is recommended. This is strong additional transparency, though it omits details like pagination.

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 compact sentences with no filler. The first front-loads the purpose, the second bundles three important operational constraints efficiently.

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?

The description covers critical operational details (timezone, availability, caching) and indicates a flat list result, but it does not describe return fields or the semantics of organization_ids. Given there is no output schema, this leaves the agent partially under-informed.

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 0%, so the description must compensate for parameter documentation. It indirectly explains 'phone' and 'last N days', but never mentions the required organization_ids parameter nor the days parameter's default of 7. This leaves a key parameter undocumented.

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 a specific verb and resource: retrieve customer orders by phone over the last N days as a flat list. It is clear about the tool's scope, but it does not distinguish it from closely related siblings like deliveries_retrieve__get_deliveries_by_delivery_date_and_phone or deliveries_retrieve__get_delivery_history_by_date_and_phone.

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 provides operational advice (cache results, quota consumption, 7-day availability) but gives no explicit guidance on when to choose this tool over alternatives. With many similar deliveries_retrieve siblings, the lack of selection criteria is a significant gap.

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