ddb_get_spell

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

The description adds the login requirement ('Requires login'), which is beyond the readOnlyHint and openWorldHint annotations. It also clarifies the tool's scope (compendium-wide, not limited to a character's spells). This provides useful behavioral context without contradicting the 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 is two sentences: the first conveys the core purpose, the second adds two important clarifications (scope and login requirement). Every word earns its place, with no redundancy or padding.

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?

This is a simple, single-parameter, read-only tool. The description covers the essential information needed for correct invocation: what it does, that it's not limited to known spells, and that login is required. With full schema coverage and annotations, no critical details are missing.

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 schema already fully documents the only parameter 'name' with description, minLength, and example. The description adds no additional parameter-specific meaning, so it relies on the schema's 100% coverage. Baseline of 3 is appropriate.

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's function: 'Get the full description of any spell in the D&D Beyond compendium by name.' It uses a specific verb ('Get') and resource ('full description of any spell'), and the phrase 'Not limited to a character's known spells' differentiates it from character-specific spell lookups.

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 clear context: it is for retrieving full spell details from the compendium, not limited to a character's known spells, and it explicitly notes 'Requires login' as a prerequisite. While it doesn't name alternative tools like ddb_search_spells, the 'by name' phrasing implies you already know the spell name, giving reasonable usage guidance.

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