ddb_search_classes

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

Annotations already indicate read-only and open-world behavior. The description adds context about login requirement and the scope of results (hit die, spellcasting, subclasses), but does not disclose return format, pagination limits, or other behavioral details beyond what annotations provide.

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 two concise sentences, front-loading the primary purpose before stating the login prerequisite. Every word adds value, with 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?

Given the tool's simplicity, good annotations, and complete schema, the description covers the essential purpose and prerequisite. It does not fully describe the return format, but that is partially implied by the mention of hit die, spellcasting, and subclasses. It is complete enough for effective selection and invocation.

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 has 100% description coverage for all three parameters (name, limit, offset), so the description does not need to add parameter-level detail. It adds no extra meaning beyond the schema, which already defines each parameter clearly.

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 classes and specifies the key content (hit die, spellcasting, subclasses). This distinguishes it from sibling tools like ddb_search_spells or ddb_search_monsters, which target different entity types.

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 gives a clear prerequisite (requires login and to run ddb_login first) but does not explicitly compare to alternative tools or state when not to use it. The usage context is implied by the resource type, but no exclusions or alternatives are mentioned.

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