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

Beyond the annotations, the description explains AND/OR filter combination, inclusive range semantics, exclusion of documents lacking a filtered field, response fields total and hasMore, result shape {name, uuid}, follow-up tool usage, and the bridge module version requirement. These are substantive behavioral details for correct invocation.

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 front-loaded with purpose, then organized into critical data formats, filter behavior, response shape, and an example. Despite its density, every section supports correct use of a 14-parameter tool and no content is redundant with the schema.

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 complex 14-parameter search tool with no output schema, the description supplies the missing response shape, pagination fields, follow-up workflow, filter logic, data formats, domain restriction, and an example. It provides enough context for an agent to call and use the tool correctly.

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 schema already documents all 14 parameters. The description still adds valuable semantics beyond the schema: price is normalized to gp, weight is in lb, decimals are allowed, ranges are inclusive, and filters combine as AND across fields and OR within arrays.

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 states a specific verb and resource: search COMPENDIUM packs for Item documents using D&D 5e structured filters. It scopes the tool to dnd5e worlds and explicitly identifies it as the compendium counterpart of world-item-filter, which helps separate it from unrelated siblings.

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 gives clear context for use: dnd5e worlds only, compendium item search, and follow-up paths via uuid-resolve or compendium-browse with IDs. It does not explicitly compare against compendium-search or state when not to use this tool, so it falls short of full when/when-not guidance.

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