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

No annotations are present, so the description carries the full burden. It states the operation and sorting options but does not disclose default behavior (e.g., default sort 'active' from schema) or any pagination/limit defaults. It is not misleading but lacks depth on side effects or output structure.

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?

One concise sentence, front-loaded with the verb and resource, and no filler. Every word earns its place.

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 tool with no annotations and no output schema, the description is minimal. It omits return format, pagination behavior, or any default limit. Given the agent needs to call it correctly, this is incomplete for a list operation with optional parameters.

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 description must compensate. It partially explains 'sort' by mentioning 'recent activity or creation time' (matching the enum), but does not explain 'limit' or its constraints. The schema provides constraints, but the description adds limited additional meaning beyond the enum mapping.

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 uses a specific verb 'List' and clear resource 'forum topics', and distinguishes by sorting criteria. It is unambiguous and separable from siblings like get_topic (single topic) and create_topic (creation).

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 usage for listing multiple topics but does not explicitly state when to choose this over alternatives like get_topic or search. No when-not-to-use guidance or exclusions are provided; the context is clear but not fully explicit.

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