ddb_search_races

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

Beyond the readOnly and openWorld annotations, the description discloses the login requirement and clarifies the scope (all races/subraces including homebrew, not character-specific). This adds meaningful behavioral context such as authentication needs, which is valuable for an agent.

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 compact and front-loaded with the core action. Each clause serves a purpose: stating the function, clarifying scope, and noting the auth prerequisite. No wasted words.

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 search tool with full schema coverage and read-only annotations, this description is complete. It covers purpose, scope, and prerequisites, leaving no critical gaps in understanding how to invoke it.

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 input schema already describes all three parameters (name, limit, offset) with complete, self-explanatory descriptions. The tool description does not add additional parameter semantics, so the baseline score of 3 is appropriate given full schema coverage.

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 it searches D&D Beyond races and subraces, including homebrew, and explicitly notes it is not character-specific. This distinguishes it from character-related tools and other search tools, making the purpose unambiguous.

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?

It provides clear context by specifying that it covers all races/subraces and is not character-specific, plus the prerequisite to run ddb_login first. However, it does not explicitly name alternative sibling tools for when not to use this one, so it lacks exclusionary guidance.

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