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

With no annotations provided, the description carries the full burden. It successfully discloses the community-sourced nature of the data ('from the community'), but omits behavioral details like rate limits, search fuzziness, or how it handles the optional ID vs name parameters (both are optional per schema, but the description doesn't clarify usage patterns).

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 exactly two efficient sentences with zero waste: the first establishes purpose, the second establishes usage context. It is appropriately front-loaded and sized for the tool's complexity.

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 the tool's straightforward purpose and complete input schema, the description adequately covers the primary use case. It could be improved by clarifying the optional parameter relationship (ID vs name) or describing the return format (forum threads vs posts), but it is sufficient for agent selection.

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 100%, providing the baseline score of 3. The description does not add semantic context beyond the schema (e.g., explaining that both parameters are optional or when to prefer ID over name), but it doesn't need to compensate for missing schema documentation.

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 provides a specific verb ('Search'), resource ('BoardGameGeek rules forums'), and outcome ('find answers and clarifications from the community'). It clearly distinguishes this from siblings like bgg-search (general) and bgg-details (game metadata) by specifying the 'rules forums' scope.

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 includes explicit positive guidance ('Use when users ask rules questions about board games'). However, it lacks negative guidance or explicit alternatives (e.g., when to use bgg-details instead for official rulebooks vs community interpretations).

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