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

With no annotations, the description carries the full behavioral burden and delivers almost nothing: no indication of result format, ordering, pagination, or what happens when search and letter are combined. Only the vague 'internal' marker hints at any access constraint, and it is unexplained.

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 single sentence is short and front-loads the resource, but the '[WORD · internal]' prefix is opaque noise that consumes space without informing selection or invocation.

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 three-parameter tool with zero schema descriptions, no annotations, and no output schema, the description leaves too much unspecified: it never explains the limit/letter/search semantics or the shape of returned entries. An agent could guess, but not confidently.

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 coverage is 0% for all three parameters (limit, letter, search), and the description does not compensate: it never mentions the limit, the letter-based browsing, or how search interacts with them. The phrase 'people, places, terms' loosely gestures at what can be searched but adds no parameter-level meaning.

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 verb (browse/search) and a resource (Easton's Bible Dictionary) with a scope hint (people, places, terms), so the general purpose is graspable. However, the name 'characters_browse' suggests people only, while the description claims places and terms too, and it does nothing to distinguish itself from sibling tools like search, lookup, define, or character_get.

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?

There is no statement of when to use this tool versus alternatives, despite siblings such as search, lookup, define, character_get, and original_words covering overlapping territory. The '[WORD · internal]' tag implies some internal restriction but never explains it.

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