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

With no annotations, the description carries the burden, and it discloses that the tool is free, updates daily, is cert-verified, and reports observed market census rather than pop reports. It could be more explicit about read-only behavior or response format, but the behavioral context is largely covered.

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 well organized, leading with the core purpose rethen cost/update details and use cases. Minor jargon and parenthetical asides add a bit of clutter, but each sentence earns its place.

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 zero-parameter read-only summary tool, the description covers output fields, update cadence, cost distinction, exclusions, and recommended usage. Nothing essential is missing for an agent to select and invoke it 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?

The tool has zero parametersheb, so schema coverage is effectively complete. The description adds value by explaining what output dimensions the census summary includes, which is the relevant information an agent needs.

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 explicitly states that this tool returns census totals across PSA/BGS/CGC/TAG, including unique certs, cards covered, grader mix, and active-30d counts. It differentiates itself from the per-card paid census, so an agent can identify the tool's scope and output.

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 provides explicit use cases: sizing supply behind a grade or judging how thin a slab market is before trusting an ask. It also clarifies the alternative per-card paid census and the NOT-pop-report exclusion, giving clear selection guidance.

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