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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes beyond them by disclosing the billing behavior (one call regardless of item count) and the mandatory source citation, which are operationally meaningful and not derivable from structured fields.

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?

Front-loaded with the core purpose and the cost/citation constraints before the return shape. The inline object notation is dense but compact, and it is justified because no output schema exists. Minor cost: the return shape occupies more than half the text.

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 no output schema, the description carries the full burden of describing returns and does so precisely: field-by-field shape, the meaning of 'figure', the ranking-item edge case (top-ranked place named in detail), and the fact that topics and publishers have no figure. Nothing an agent needs to call and interpret this correctly is missing.

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% and the single 'id' parameter already documents its origin ('Collection id from list_collections'). The description adds no format, prefix, or lookup guidance beyond that, so the baseline 3 applies.

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 ('Read one collection') and immediately scopes it ('with the live figure of each item'), which cleanly separates it from list_collections (enumeration) and get_value (single figure). An agent can distinguish it from all siblings without opening a schema.

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 only implied: you call it to inspect a collection's contents, presumably after list_collections. The description adds a real constraint ('Counts as one call of the monthly allowance, however many items the collection holds') and a citation obligation, but never states when to prefer this over get_value, get_series, or list_collections.

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