ddb_rate_encounter

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

The annotations (readOnlyHint: true, openWorldHint: true) already establish that this is a safe read-only operation. The description adds useful behavioral context beyond annotations: the automatic compendium lookup, the behavior change based on rules_edition, and the ability to supply 'cr' directly for homebrew. It does not disclose potential network calls or error handling, but the annotations lower the burden.

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 long, front-loaded with the core purpose, and every clause adds value: default edition, edition switching, and homebrew handling. 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?

The description covers the tool's main inputs, behavior, and output categories (Low/Moderate/High and Easy/Medium/Hard/Deadly) even though there is no output schema. It lacks details on potential failure modes (e.g., monster not found) but is otherwise complete for a lookup-based calculation tool with strong annotations.

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%, so the baseline is 3. The description mostly repeats information already in the schema: the 2024 vs 2014 behavior is in the rules_edition parameter description, and the 'cr for homebrew' note is in the cr field description. While it adds a brief clarification about automatic monster lookup, it does not significantly extend beyond the schema.

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 purpose with a specific verb and resource: 'Rate the difficulty of a D&D encounter.' It also details the two rule editions (2024 and 2014). However, it does not explicitly distinguish this tool from the sibling tool 'ddb_encounter_cr', so it lacks explicit sibling 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 clear guidelines on when to use each edition: 'Defaults to 2024 XDMG rules' and 'Set rules_edition to 2014 for the classic DMG XP threshold method.' It also explains how to handle homebrew monsters via the 'cr' parameter. It does not mention alternatives or when not to use the tool, so it stops short of a 5.

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