ddb_search_site

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

Annotations already declare readOnlyHint=true and openWorldHint=true, which tell the agent this is a safe, read-only operation that may access external data. The description adds no additional behavioral context (e.g., result format, live-site nature), but it does not contradict the annotations, so it meets the minimum standard.

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 sentence that front-loads the verb ('Search') and resource ('D&D Beyond') and lists the covered categories. Every word adds value, and there is no redundancy or filler.

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 two-parameter search tool, the description combined with the schema and annotations is adequate. However, it does not explain what the tool returns (no output schema exists) or guide the user toward specialized sibling tools for narrower searches, leaving some contextual gaps.

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%; both 'query' and 'category' have descriptive text, including examples and an enum. The tool description itself adds no parameter semantics beyond what the schema already provides, matching the baseline for high 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 the tool searches D&D Beyond for multiple content types (spells, monsters, magic items, races, classes, feats) with a specific verb and resource scope. However, it does not distinguish itself from the many sibling category-specific search tools (e.g., ddb_search_spells, ddb_search_monsters), so it's clear but lacks explicit differentiation.

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 provides no guidance on when to use this general search tool versus the specialized sibling tools like ddb_search_monsters or ddb_search_spells. It does not mention that this tool covers multiple categories, nor does it suggest using category-specific tools for narrower searches.

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