Listing analytics

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds context by stating 'Read-only analytics' and specifying that it returns extended statistical metrics with flexible grouping, filters, and sorting, plus the limit constraint. This adds value beyond annotations, though it could further describe the output structure.

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 sentences with high information density: first sentence states purpose and key features, second sentence provides usage guidance. No unnecessary words, front-loaded with core purpose.

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 tool with 9 params, 6 required, no output schema, and annotations present, the description covers purpose, usage guidance, key constraints, and differentiator. It lacks details on output format but is largely complete given the schema and annotations.

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 coverage is 100% with detailed descriptions for each parameter. The description briefly summarizes key parameters (grouping, filters, sorting, metrics) and mentions limit ≤ 1000, but adds limited new meaning beyond the schema. Baseline 3 is appropriate.

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?

Clearly states the tool returns extended statistical metrics for profile/listings over a period, with examples (views, contacts, presenceSpending). The title 'Listing analytics' reinforces the resource, and it distinguishes from the sibling items_post_item_stats_shallow by specifying advanced capabilities like filters and sorting.

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?

Explicitly advises when to use this tool over items_post_item_stats_shallow: when filters by category/employee, sorting by a metric, or presence-spending metrics are needed. Also mentions limit ≤ 1000, providing clear guidance.

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