analytics_funnel

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds context about the specific funnel steps and abandoned value, which is useful. However, it doesn't disclose any other behavioral traits like response format or aggregation details, so it meets basic expectations without exceeding them.

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, packed sentence that front-loads the main purpose and lists the key output components. There is no waste or redundancy; every word contributes to understanding.

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 2 simple parameters and no output schema, the description covers the core function well (funnel steps and abandoned value). However, it lacks details on parameter semantics and does not specify the response granularity or format, leaving some gaps for a tool with no other documentation.

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 for parameter understanding. It only says 'for a date range', which hints at the 'from' and 'to' parameters but does not explain their format, inclusiveness, or whether they are required. This is minimal compensation for the lack of schema details.

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 tool's function: cart funnel analytics for a date range, listing the specific stages (viewed, added to cart, checkout, purchase) and abandoned value. This is a specific verb+resource and distinguishes it from sibling CRUD and reporting tools like sales_report.

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 implies usage context by specifying 'for a date range' and the exact funnel metrics, indicating it should be used when cart funnel analysis is needed. However, it does not explicitly mention when to use an alternative (e.g., sales_report for overall sales), so it has clear context but no exclusions.

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