shopify_order_countCount orders in a date range without loading order details, with an optional status filter for quick reporting.
Lightweight order count for a date range without fetching order details.
| Name | Required | Description | Default |
|---|---|---|---|
| date_to | Yes | End date YYYY-MM-DD | |
| date_from | Yes | Start date YYYY-MM-DD | |
| status_filter | No | Extra filter e.g. financial_status:paid |
Changes observed during successful MCP inspections.
v4.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that it avoids fetching order details (an efficiency trait), but says nothing about count limits, status scoping defaults, or return shape.
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?
A single short sentence with the key distinction ('lightweight', 'count') front-loaded and zero filler.
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 counting tool with annotations and full schema coverage this is adequate, but with no output schema it never states what is returned (a bare integer?) or whether the count respects a default status filter, leaving a small but real 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 description coverage is 100%, so date_from/date_to/status_filter are already documented in the schema. The description echoes the date-range concept but adds no syntax, default, or semantics for status_filter beyond what the schema provides.
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?
States a specific verb and resource ('order count') scoped to a date range, and implicitly distinguishes itself from detail-fetching siblings like shopify_list_orders via 'without fetching order details'. No sibling is named explicitly, so it misses the top band.
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?
'Lightweight ... without fetching order details' implies you should use it when only a number is needed, but no alternative tool is named and there is no stated when-not guidance beyond the efficiency hint.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.