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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds real behavioral context beyond that: it scans paginated ItemsSelling results server-side, returns intersection counts, and imposes an attribution-footer and data-accuracy contract. Good additional disclosure, though no pagination/rate-limit or return-shape detail.

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 first two sentences are front-loaded and useful, but the attribution-footer instruction and the long generic 'Data accuracy contract' boilerplate are cross-cutting policy text that inflates the definition without describing this tool. Roughly half the text is reusable boilerplate rather than tool-specific.

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 an 11-parameter, no-required-parameter aggregation tool with no output schema, the description conveys the core behavior (aggregate and intersection counts from server-side pagination) and safety is covered by annotations. Return structure is unspecified, but the essential call context is present.

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 73%, so the schema documents most parameters itself. The description only loosely gestures at filters ('listings ending within the requested window that also have watchers') and adds no per-parameter syntax or default semantics. 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?

States a specific verb and resource ('Return aggregate counts for the authenticated seller active GunBroker listings') and clarifies it produces compact totals 'instead of raw listing pages', which distinguishes it from the list_gunbroker_items_selling sibling without naming it explicitly. Clear but stops short of naming the alternative tool 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?

Usage is implied via 'returns compact totals instead of raw listing pages', suggesting it is the aggregate alternative to raw listing tools, but there is no explicit when-to-use/when-not statement or named alternative. An agent can infer intent but is not guided decisively.

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