Listing statistics

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

Description declares 'Read-only analytics' which matches annotations (readOnlyHint, destructiveHint=false). Adds extra behavioral info: limits (200 listings, 270 days) beyond annotations. No contradiction.

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, front-loaded with core purpose, then metrics, alternatives, and limits. No 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?

For a 6-param tool with no output schema, the description explains purpose, usage context, alternatives, and constraints. Lacks return format details, but acceptable given no output schema.

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. Description adds grouping context (day/week/month) but mostly summarizes schema. Baseline 3 is appropriate as description adds marginal value over schema.

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 counters (shallow statistics) for listings over a period, listing exact metrics (unique views, contacts, favorites). It distinguishes from siblings by naming alternatives for extended analytics (items_post_item_analytics) and calls (items_post_calls_stats).

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 states when to use this tool vs alternatives: for extended analytics or calls, point to specific other tools. Also provides limits (max 200 listings, 270 days back) to guide proper usage.

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