list_node_topics

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

With no annotations, the description carries the behavioral disclosure burden. 'List' suggests a read-only operation and 'inside a node' clarifies scope, but it does not mention pagination behavior, return shape, or whether the listing includes nested subnodes.

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 a single, front-loaded sentence with no filler. The parenthetical '(nested community)' adds relevant disambiguation, though the overall terseness contributes to the lack of parameter guidance.

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?

Given no output schema, no annotations, low schema coverage, and four parameters, this one-line description is incomplete. An agent is left without clear guidance on required parameter semantics or expected return data.

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 only 25%, with only the sort parameter documented. The description adds the useful clarification that a node is a 'nested community,' but it does not explain slug, node_id, or page semantics, leaving most parameters under-specified.

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 specific verb and resource: 'List topics inside a node (nested community).' This clearly differentiates the tool from siblings like list_latest_topics and list_top_topics, which are not scoped to a node.

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 implies when to use this tool: when topics within a specific node/nested community are needed. However, it does not explicitly contrast with alternatives such as list_category_topics or list_latest_topics, nor does it state when not to use it.

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