shopify_landing_page_analysis

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

With no annotations provided, the description must carry the full burden of behavioral disclosure, but it only hints at a specific counting method for new customers. There is no mention of whether the operation is read-only, what data is returned, pagination behavior, or any side effects. The description is insufficient to understand the tool's behavior.

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 short phrase, which is concise but lacks structure: no sentences, no clear subject-verb-object. It is minimally acceptable but could be improved with a proper sentence.

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 tool has 5 parameters, no output schema, and no annotations, the description is far too brief. It does not explain the output format, pagination, or the meaning of 'accurately counted new customers'. The tool's functionality is under-specified for an agent to use correctly.

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 schema has 0% description coverage for its 5 parameters, and the tool description adds no additional meaning beyond the parameter names and types. For example, 'query' and 'limit' are not explained. The description mentions the sortable metrics (netSales, orders, newCustomers) but does not clarify their usage or how the query parameter works.

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 the output concerns 'landing-page performance by sales, orders, and accurately counted new customers', which broadly indicates the tool's focus. However, it lacks a verb (e.g., 'get' or 'list') to clearly express the action performed, and the phrase 'by' is ambiguous as to whether it filters or groups results. The purpose is somewhat clear but not actionable or precise.

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?

The description provides no guidance on when to use this tool versus the many sibling tools (e.g., shopify_sales_by_source, shopify_attribution_quality_summary). There is no mention of context, prerequisites, or alternatives, leaving the agent to guess when this tool is appropriate.

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