List forum sections

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds non-obvious behavioral context: the large result volume without filters and the parent_node_id field that allows rebuilding the hierarchy. It does not discuss pagination or limits, so it stops short of 5.

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 sentences, front-loaded with purpose, then usage routing, then the caveat. Every sentence carries information the agent needs; nothing is redundant.

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 return-value burden and does so: default fields plus the extra fields unlocked by detailed/include_prefixes. Hierarchy, volume, and downstream tool usage are all covered for a zero-required-param listing tool.

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 coverage is 100%, so the baseline is 3. The description goes further by explaining the intent behind parent_category_id/parent_forum_id (narrowing scope) and clarifying that parent_node_id identifies the parent section or category, adding semantics the schema alone doesn't convey.

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 ('Lists LOLZTEAM Forum sections') and enumerates the returned fields (IDs, titles, thread counts). It is clearly distinguishable from the sibling forum_list_categories and from thread-level tools.

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?

Explicitly routes the agent: forum_id values feed forum_list_threads and forum_search, and it warns that an unfiltered call returns several hundred sections, recommending parent_category_id or parent_forum_id first. Both when-to-use and the narrowing strategy are stated.

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