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

Annotations declare this is a non-read-only, open-world, non-idempotent operation, but they say nothing about cost or execution model. The description adds genuinely new behavior: asynchronous background execution, a batch id return, and per-row charging only on a successful match. It does not address whether re-submitting the same URLs creates a duplicate batch, which matters given idempotentHint=false.

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?

Three short sentences with the core action, the return/polling contract, and the billing rule, all front-loaded. Nothing is repeated from the schema or annotations without added meaning.

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?

There is no output schema, and the description compensates by stating the return value ('a batch id') and the follow-up tool. Cost model and the 500 limit are covered; the only real gaps are idempotency/deduplication and an explicit pointer to the single-URL alternative.

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 67% and the schema already documents every property, including the profile-URL-only constraint and the platform enum's 'same price either way' note. The description adds no per-parameter meaning beyond restating the 500 cap already encoded as maxItems; baseline 3 applies when the schema does the heavy lifting.

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 specific verb and resource ('Queue up to 500 profile URLs to look up in the background') and names the async pattern that distinguishes it from the synchronous sibling lookup_creator. It never names lookup_creator explicitly, so the differentiation is implied rather than asserted.

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?

Gives clear usage context: use this for bulk, background work, and poll the result with get_batch, which is named. It stops short of saying when to prefer lookup_creator for a single URL, so the alternative routing is left to inference.

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