Get Customer Activity Timeline

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuine behavioral context beyond that: events are returned newest first and an empty list is a legitimate outcome for many customers, which prevents the agent from treating an empty result as a failure.

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 resource definition, with the empty-result caveat placed last where it belongs. Zero wasted words.

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?

With no output schema, the description should carry more of the return-value burden than it does; it covers ordering and the empty case but says nothing about the shape of an event, the limit/pagination semantics, or error conditions. Adequate but with clear gaps.

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?

Only 50% of parameters are documented in the schema (limit has no description), and the description adds nothing about either parameter. It never mentions the limit cap of 250 or pagination behavior, so the description does not compensate for the coverage gap.

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 names a specific resource ('activity timeline for one customer') and scopes it by analogy to the Shopify admin page. It doesn't explicitly distinguish itself from sibling shopify_get_customer or shopify_search_customers, but the resource is unambiguous.

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?

Usage is implied by the analogy to the admin page timeline, but there is no explicit when-to-use guidance and no mention of the obvious alternative shopify_get_customer for profile data. The agent must infer that this is the historical-events view versus a profile lookup.

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