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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Look up', implying a non-mutating read, but does not reveal data sources, output shape, failure behavior, rate limits, or whether results are real-time or cached.

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 front-loads the core verb and entity types, making it easy to scan. The leading 'Entity Lookup:' label partly restates the tool name, but overall there is no unnecessary filler.

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?

With no annotations, no output schema, and three weakly differentiated string parameters, an agent lacks enough context to know what input format to provide or what kind of result to expect. The description does not resolve ambiguity with the sibling x402-entity-link and is therefore incomplete for confident tool selection and invocation.

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 is 3 even without parameter details in the description. However, the schema notes like 'Name to process' and 'Input to process' are generic, and the description does not clarify which parameter to use for company, person, or token lookups.

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 uses a clear verb ('Look up') and identifies the resource scope (company, person, token), so an agent can tell what the tool does. However, it does not distinguish this tool from the near-sibling x402-entity-link or other entity-related lookup tools, which prevents a 5.

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 about when to use this tool versus alternatives such as x402-entity-link, company-check, or token-intel. The description offers no use-case context, exclusions, or prerequisites, leaving the agent to infer when this tool is appropriate.

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