Get Forum Categories (Optional)

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

Annotations already mark the tool as readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false. The description adds critical behavioral context: the tool depends on a separately running Discourse MCP server, and if not available, recommends an external workaround. No contradictions with annotations.

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 consists of two efficient sentences: the first defines the core purpose, and the second explains the optional dependency and fallback. No superfluous information, well 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 no-parameter, no-output-schema tool with rich annotations, the description covers purpose, dependency, and alternative. It does not describe the return format (e.g., structure of categories), which would be beneficial but not critical. Complete enough for practical use.

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?

The tool has zero parameters, so schema coverage is 100%. The description implicitly indicates that all categories are fetched without filters, which aligns with the lack of parameters. Baseline for 0 parameters is 4, and no additional parameter semantics are needed.

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 states 'Get all available categories from the VeBetterDAO Discourse forum,' specifying the verb (get) and resource (categories). It differentiates from sibling tools like getDiscourseLatestTopics, getDiscoursePost, getDiscourseTopic, and searchDiscourseForum by focusing solely on categories.

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 states that the tool requires the Discourse MCP server running separately and provides a clear fallback: suggest visiting the URL to browse categories. This tells the agent when to use the tool and what to do if it's unavailable.

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