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

With no annotations provided, the description carries the full burden of disclosing behavior. It only says 'Browse/search' which is already implied by the tool name. It does not mention output format, pagination behavior, whether search is exact/fuzzy, or any other operational details that would help an agent anticipate side effects or limitations.

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 a single, front-loaded sentence that directly states the tool's purpose. It avoids unnecessary words and is appropriately sized for its simplicity. Every word contributes to understanding.

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 tool has no annotations, no output schema, and no parameter documentation. The description names the resource and scope, but omits crucial context such as how to use the parameters, what the response will look like, and how it differs from related tools. For a tool with three parameters and no schema descriptions, this is incomplete.

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 0%, so the description must compensate by explaining the parameters. It does not mention 'limit', 'letter', or 'search' at all. The parameter names are generic and the schema only provides types and odd ranges (e.g., limit min/max of ±1e12), leaving the agent to guess their meaning and usage.

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: 'Browse/search Easton's Bible Dictionary' with explicit scope of 'people, places, terms'. This specific verb-resource pairing distinguishes it from sibling tools like character_get (which likely fetches a single character) or bible_places (which might be a different resource).

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?

No guidance is provided about when to use this tool versus alternatives. The description only states what the tool does, not when it should be preferred over other search/browse tools (e.g., search, cards_browse). There are no exclusions or alternative recommendations.

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