lookup_html_entity

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

No annotations are provided, so the description must convey behavioral traits. The only behavioral information is the cost of $0.001 USDC, but there is no disclosure of whether the tool is read-only, what it returns, error behavior, or any side effects. This is insufficient for safe 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 short and free of unnecessary words, but the first six words are a restatement of the tool name, and the 'Other Utilities tool' phrase is generic filler. While concise, the content does not earn its place because it adds no substantive information.

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 output schema and the input schema is generic, so the description is the only source of contextual information. It fails to explain the input requirements, output format, or the exact range of lookups supported, making it inadequate for reliable use.

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?

The schema contains a single generic 'params' object with no meaningful key definitions, and the description adds no parameter semantics. The agent has no way to know what fields to provide (e.g., character, entity name, numeric code). Despite the 100% schema coverage, the coverage is of a generic container, so the description does not help.

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 begins with 'lookup html entity', which directly repeats the tool name without providing any additional detail about what the tool actually does. It does not distinguish this from sibling tools like html_escape or lookup_http_code, and the generic 'Other Utilities tool' label offers no functional clarity. This is a tautology rather than an explanatory description.

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 guidance on when to use this tool. It does not mention any prerequisites, use cases, or alternative tools, leaving the agent to infer the intended invocation context solely from the name.

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