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

No annotations are provided, so the description carries the full burden. It says nothing about whether this hits a network source, whether x402 payment/auth is required, caching, rate limits, or what data a lookup yields. For an unannotated tool this is a complete transparency failure.

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?

A single short sentence that is front-loaded with the verb and resource. Efficient, though it is under-specified rather than genuinely concise — there is little content to be concise about.

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 3 undocumented optional parameters, no annotations, and no output schema, the description leaves nearly everything unanswered: input format, entity-type selection, and result shape. It is not complete enough for an agent to invoke 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% and all three params (name, input, company) are undocumented. The description's mention of 'company, person, token' loosely hints at lookup modes but does not explain the distinction between the 'name', 'input', and 'company' parameters or which to use when.

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?

States a verb ('Look up') and resource ('an entity') with examples (company, person, token), which is clearer than a bare name. However, it does not distinguish this from the many lookup-adjacent siblings (x402-entity-link, x402-company-check, x402-token-intel), nor does it say what a lookup returns.

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 when-to-use guidance, no prerequisites, and no mention of alternatives despite a sibling list packed with overlapping entity/company/token tools. The agent must infer the use case entirely.

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