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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context: the call is free/requires no payment, and it discloses the shape of what comes back (per-function inputs, output fields, price per record and per 100 records, language support).

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 tight sentences with no filler; the billing reassurance ('Free, no payment needed') is front-loaded ahead of the functional detail. The middle sentence is dense but earns its place by enumerating the catalog's contents.

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, but the description compensates by specifying what the response contains (inputs, output fields, price per record/100 records, language acceptance) for both the all-functions and single-function cases. For a single-optional-param catalog tool, nothing an agent needs to call it correctly is missing.

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% and the single optional 'function' parameter already documents the enum, its example, and the omit-to-list-all behavior in the schema itself. The description repeats the same idea (a function name yields its full details vs. omitting lists all) without adding syntax or format beyond the schema.

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+resource: it lists the enrichment functions available to interzoid_enrich_records, and enumerates exactly what each entry contains (output fields, inputs, price, language support). This clearly distinguishes it from the sibling per-function tools (e.g., interzoid_business_info) which execute a single enrichment.

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 an explicit trigger: 'Call it to choose the right function before enriching records,' which positions it as a prerequisite/discovery step for interzoid_enrich_records. It does not state a when-not condition or name alternative discovery paths, but the sequencing guidance is unambiguous.

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