chitchats_list_shipments

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

Annotations declare readOnlyHint=true, so the safety profile is covered. The description adds 'Supports pagination' and lists filter dimensions, but these are largely reflected in the schema. It doesn't disclose additional behavioral details like rate limits or default response structure beyond the schema.

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 three short sentences, front-loaded with the main action, and contains no fluff. Each sentence earns its place: purpose, usage, and pagination.

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 provides essential context for a read-only list/search tool with 7 parameters and no output schema. It mentions pagination and common filters, which is sufficient for basic usage. It doesn't describe the response format, but the tool name and read-only nature imply a list of shipments, and the schema explains parameters.

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 each parameter is already documented. The description reiterates filter categories (order ID, status, date range, batch) but doesn't add new meaning beyond the schema. Baseline 3 applies.

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 starts with a specific verb+resource: 'List and search shipments with filters.' It clearly distinguishes from siblings like get_shipment (single) and count_shipments (count) by indicating a listing/searching operation.

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 says 'Use this to find shipments by order ID, status, date range, or batch,' providing clear when-to-use context. It doesn't mention when not to use it or name alternative tools, but the use case is clear enough.

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