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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that lookups are batched; it says nothing about behavior for missing/unknown identifiers, partial results, or result ordering, which would be the genuinely additive context here.

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?

Two short sentences, purpose front-loaded, with a concrete invocation example that earns its place. No filler, though the example is the only elaboration and slightly narrows the framing to a single-item list.

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?

An output schema exists, so return values need not be explained. However, for a tool with a nested optional 'catalog' object and zero required params, the description leaves open what that object supplies and how batched misses are handled, which is a meaningful gap for correct 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 baseline is 3. The example 'lookup_catalog(ids=['agd-pass-2000'])' usefully shows ID string format, but the second parameter 'catalog' is described only as 'Optional catalog context' in the schema and receives no clarification in the description, leaving an opaque nested object unexplained.

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 ('Batch lookup catalog items') plus the keying mechanism ('by product identifier list'), which separates it from the sibling search_catalog by making the batch-by-ID nature explicit. It does not explicitly name search_catalog as the alternative, so it stops short of 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?

The word 'Batch' and the id-list framing imply usage (retrieving many known items at once), but there is no explicit statement of when to prefer this over search_catalog or get_product. The agent has to infer that this is the bulk-fetch path for known identifiers.

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