List forum posts

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

Annotations declare readOnlyHint=true, and the description does not contradict this. The description adds minimal behavioral context beyond the annotation—only mentioning tag filtering and archived inclusion, which are parameter semantics rather than behavioral traits like pagination or rate limits.

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 concise phrase with no filler. It front-loads the core concept and is easy to scan.

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 list tool with no output schema, the description covers the main function and optional filters, but it omits details like pagination, sorting, or the return payload structure. It is minimally adequate but leaves the agent to infer behavior from the schema and annotations.

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 descriptions cover forum, guild, and tag; the description adds meaning for 'tag' (filterable) and 'include_archived' (optionally archived too), which is useful since include_archived has no schema description. Forum and guild are already documented in the schema.

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 'Posts in a forum, filterable by tag, optionally archived too' clearly indicates the tool retrieves forum posts, and the title reinforces this with 'List forum posts'. It is specific to forum posts and distinguishes from siblings like create_forum_post or list_threads, though it does not explicitly name alternatives.

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 conveys that this tool is for viewing forum posts, especially with tag filtering and archived inclusion, but it offers no explicit guidance on when to prefer it over related tools like list_threads or read_messages. Usage is implied rather than stated.

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