spell_search

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

With no annotations provided, the description carries the full disclosure burden. It does disclose the key behavior: the tool returns a list of matching entries rather than a single object. It does not cover edge behaviors such as empty results, pagination, or matching semantics, but the search-only nature and list output are sufficiently transparent for typical use.

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 with no filler. The first sentence states the action and output, and the second sentence provides routing guidance, making it efficient and easy to parse.

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 a complete schema and no output schema, the description covers the important selection and invocation context: what is searched, what is returned, and when to use omnisearch instead. It could be slightly richer about result entry shape or default behavior, but the schema already covers the main invocation details.

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 applies and the schema already documents all seven parameters. The description adds no parameter-level detail beyond indicating that the query searches by name, but no information is lost because the schema is complete.

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 opens with a specific verb and resource: "Search D&D 5e spells by name." It also states the output form, "Returns a list of matching entries," and distinguishes itself from omnisearch by noting the condition for using the broader tool.

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 explicitly tells the agent when to use this tool: when the content type is known. It also names an alternative, omnisearch, and gives the exact condition for switching to it, which is clear routing guidance among many sibling search tools.

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