Get Recently Created or Updated Consignments

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns consignments with pagination and optional filters, which is consistent with a safe read operation. It does not contradict annotations and adds moderate context beyond them.

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 extremely concise: a single-line purpose followed by a clear list of arguments with types and brief descriptions. No fluff, and the most important information is front-loaded.

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?

While the description covers all parameters and purpose, it lacks details on the response format (e.g., whether it returns full consignment objects or summaries) and does not mention pagination behavior for large result sets. For a tool with no output schema, this is a notable gap.

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 coverage is low (33%), but the description explains all 9 parameters, including purpose for optional ones (e.g., 'Filter by carrier', 'Include sub-companies'). This adds significant value beyond the schema, though some parameter descriptions remain brief.

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 explicitly states 'Returns consignments created or updated within a UTC date range' and identifies the tool as 'Ideal for sync/polling workflows.' This clearly distinguishes it from siblings like machship_get_active_consignments or machship_get_completed_consignments which do not filter by modification time.

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 a clear use case ('sync/polling workflows') and implies when to use the tool. However, it does not explicitly mention alternatives or conditions when not to use it, despite the presence of many related sibling tools.

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