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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds that only IDs are returned and defines the pending condition, but it omits pagination, limits, or default behavior when no filters are supplied.

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 short sentences, front-loaded with the returned resource and followed by the optional filtering behavior. The endpoint reference adds API context without bloating the definition.

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 read-only list tool with no output schema, the description covers the return type (IDs), the pending scope, and the available filters. It could be strengthened by clarifying pagination or what happens when no filters are provided, but it is largely complete.

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?

The description maps all three parameters conceptually: customer_id filters to one customer, and due_date_from/due_date_to form a due-date range. The schema documents the date formats, and the description adds useful semantic context for the otherwise undocumented customer_id parameter.

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 resource and scope: sales orders not yet delivered, returning their IDs. It is distinguishable from general sales-order listing because of the pending/delivered condition, though it does not explicitly name its closest sibling, laudus_list_sales_orders.

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?

It indicates that customer and due-date filters are optional, implying use when pending orders are needed for one customer or a date window. It does not state when to use this instead of laudus_list_sales_orders or laudus_get_sales_order.

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