Get Recently Created/Updated Pending Consignments

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, indicating safe read. The description adds that it returns 'pending consignments' and uses UTC date range, but does not disclose pagination behavior, defaults, or response format. Given annotations cover the safety profile, this adds minimal behavioral context.

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, front-loads the main purpose, and uses a clear Args list. Every sentence adds value. It could be slightly more structured but is efficient overall.

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?

With 8 parameters, no output schema, and a sync use case, the description lacks details on pagination behavior (e.g., zero-based index, max page), response structure, or potential rate limits. This makes it incomplete for a complex retrieval tool.

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 low (38%), so the description must compensate. It lists all 8 parameters with brief descriptions like 'Pagination start' for startIndex, but does not add details like default values, bounds, or behavior beyond the schema. This is a marginal improvement over the schema.

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 'Returns pending consignments created or updated within a UTC date range. Useful for sync workflows.' This clearly identifies the tool's purpose and distinguishes it from sibling tools like machship_get_pending_consignment (single) and machship_get_recent_consignments (non-pending).

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 mentions 'Useful for sync workflows,' providing some context, but lacks explicit guidance on when not to use this tool or alternatives among the many get-consignment tools. No exclusions are specified.

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