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

With no annotations, the description carries full behavioral disclosure and does so excellently: it warns that completed purchases never enter the dataset, instructs not to derive abandonment rates or compare to order totals, and enumerates five fields that will always be null with an explanation of why. This is exactly the kind of context an agent needs to avoid misinterpretation.

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 dense but front-loads the purpose, then the report contents, then the critical universe limitation and null fields. It's a bit long due to the exhaustive metric list and null-field enumeration, but every sentence serves a purpose and there is no 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 complex analytics tool with no annotations and no output schema, the description covers the purpose, data contents, caveats, and explicit limitations. An agent has everything needed to call and interpret the tool 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?

Schema description coverage is 100%, so the schema already documents all five parameters. The description adds no parameter-level detail beyond what the schema provides; the baseline of 3 applies when the schema does the heavy lifting.

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 it returns cart abandonment analytics and enumerates the two report types (stats, top_products) with the specific metrics each contains. It distinguishes itself from siblings like get_top_products or get_orders by explicitly scoping to abandoned-checkout records, though it doesn't name competing tools directly.

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 explains the data universe (only abandoned checkouts) and lists what's never available, but does not say when to use this tool versus e.g. get_top_products or get_orders, nor does it state prerequisites. Usage is implied through the report enum but not guided.

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