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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the shape of the aggregate output (which stats are computed), but says nothing about whether the 'state/province' dimension is a required input, what the default coverage is, or how the period default affects results. With annotations doing the heavy lifting, a 3 is appropriate.

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?

A single compact sentence that front-loads the resource and enumerates the returned metrics. No wasted words, though the fragment style omits a verb and could be marginally clearer.

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 annotations covering the read-only/open-world profile and an output schema present, return values need not be explained, yet the description usefully summarizes them. For a simple one-parameter read tool it is nearly complete, missing only a note on scope (e.g., whether it returns all states at once).

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% (the single 'period' parameter is documented in the schema), so the baseline is 3. The description adds no detail about the period parameter's format or units, and notably mentions a state/province dimension that has no corresponding parameter, which could confuse invocation.

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 states a specific resource and data type ('BBB Scam Tracker state/province aggregate stats') and enumerates the metrics returned (report counts, losses, per-capita rates, YoY change, top scam types). This distinguishes it from siblings like bbb_scamtracker_search and bbb_scamtracker_detail by making clear it returns aggregates rather than individual reports, though it does not name those siblings explicitly.

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 word 'aggregate' implies use for summary/statistical queries rather than raw record browsing, so usage is inferable. However, there is no explicit statement of when to prefer this over bbb_scamtracker_search or bbb_scamtracker_detail, and no exclusions or prerequisites are given.

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