shopify_inactive_customer_summary

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

No annotations are present, so the description must carry the full behavioral burden. It only mentions windows but does not define 'inactivity', describe the output format (e.g., list vs. counts), or disclose whether calls are destructive or read-only. Limits or default behavior are not explained.

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 a single sentence with no extraneous words, but it sacrifices necessary detail for brevity. It is concise but lacks completeness.

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 no output schema, no annotations, and zero schema coverage, the description is critically incomplete. It does not explain what the summary contains, how inactivity is defined, or how parameters affect results. The agent cannot fully understand tool behavior.

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 0%, so the description must compensate. However, it does not mention either parameter ('asOfDate' or 'limit') or explain their meaning or usage. The agent gains no additional understanding from the description.

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 'Customer inactivity summary' which implies a summary resource but lacks a clear verb. It specifies fixed windows (30/60/90/180 days), giving some context, but does not clarify whether it returns counts or lists. It also fails to distinguish from siblings like 'shopify_customer_purchase_summary' or 'shopify_repeat_purchase_windows'.

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?

No guidance is provided on when to use this tool versus alternatives such as 'shopify_list_customers' or 'shopify_retention_overview'. No context on prerequisites or scenarios is given.

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