list_community_topics

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

With no annotations, the description carries the full behavioral disclosure burden. It adds one meaningful behavior—force_refresh bypasses cache and fetches fresh data—and 'List' implies a read-only operation. However, it does not disclose pagination, ordering, or other response characteristics, leaving the output schema to fill that gap.

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 concise and well structured: a single lead sentence followed by two argument definitions. There is no repetition, filler, or unnecessary detail, and the core purpose is front-loaded.

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 simple two-parameter list tool with an output schema, the mechanical details are mostly covered: purpose and both parameters are explained. The main completeness gap is the missing relationship to sibling community-topic tools, which matters for correct tool selection.

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 0%, so the 'Args' section is essential. It explains subdomain as the 'Help Center hostname' and force_refresh as cache-bypass behavior, providing real semantic value beyond the bare property names and types.

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 clearly identifies the action ('List') and the resource ('community/forum topics'), so an agent can understand the basic function. However, it does not differentiate this tool from the sibling list_community_posts, leaving the topics-vs-posts distinction implicit.

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 no guidance on when to use this tool versus list_community_posts, list_categories, or list_sections. It names no alternatives, no conditions, and no exclusions, so the agent must infer selection from the tool name and sibling names.

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