List topics

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: all_pages is bounded, each page consumes API quota, and the result is not a snapshot or guaranteed complete backup. That quota/pagination caveat is the kind of disclosure annotations cannot express.

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?

Three short, front-loaded sentences with no filler; the pass-through is trivial and the quota warning arrives early. It is slightly telegraphic but every clause carries information.

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 read-only list tool with 100% parameter coverage and annotations covering safety, the description supplies the one non-obvious operational fact (bounded paging that costs quota). Nothing critical is missing, though field-level return detail and filtering strategy are left entirely to the 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 description coverage is 100%, so the schema already documents name, page, sort, account, per_page, all_pages and max_items, including the quota caveat on all_pages. The description reinforces the all_pages/quota behavior but adds no syntax or semantics the schema lacks, 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?

The description states a verb+resource ("List topics") but the opening sentence is essentially a restatement of the tool name, and it offers no differentiation from siblings such as list_posts, get_topic, or create_topic. An agent knows it lists topics but not how it relates to other topic or list operations.

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?

There is no guidance on when to use this tool versus alternatives (e.g., get_topic for a single topic, or any search tool), nor any mentioned prerequisites or filters the caller should consider. "Reads community data" is a scope note, not usage guidance.

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