list_orders

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

No annotations are provided, so the description must carry full behavioral disclosure. It fails to mention pagination behavior, rate limits, or return value structure. Critically, it inaccurately claims 'date range' filtering is available, which is not supported by the input schema parameters.

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 brief and front-loaded with the primary action. However, the inclusion of the unsupported 'date range' parameter wastes the limited space, and the second sentence is merely a parameter list that could be inferred from the schema.

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?

Given the lack of annotations and output schema, the description should provide richer behavioral context (e.g., pagination details, default sort order, maximum limits). The inaccurate 'date range' claim further reduces confidence in the description's completeness.

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?

While the schema has 100% coverage (baseline 3), the description introduces confusion by referencing a 'date range' filter that does not exist in the schema. It adds minimal semantic value for the existing parameters beyond what the schema already documents.

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 clearly states the action (List) and resource (work orders from Shopmonkey), with sufficient specificity to distinguish from sibling list tools like list_appointments or list_customers. However, it does not explicitly differentiate from the singular get_order sibling.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., using get_order for single record retrieval) or when filtering is preferable to other search methods. No prerequisites or exclusions are mentioned.

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