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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It does well by revealing the $18 cost, the immediate return of checkout_url and order_id, and the fact that results require a separate paid follow-up call. This gives the agent crucial behavioral context beyond the bare schema.

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 concise, information-dense sentences fully describe the action, pricing, immediate response, and required next step. Every sentence earns its place and the core purpose is front-loaded.

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?

Given there is no output schema and no annotations, this description is remarkably complete: it states the required input domain, the cost, the immediate outputs, and the necessary follow-up call to retrieve the result. An agent has enough information to invoke the tool correctly and understand the paid-async workflow.

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 100% and the only parameter, target_domain, is clearly documented in the schema as 'Domain of target company to audit.' The description reinforces this with 'target company website' but adds no additional semantic meaning beyond the schema's own description.

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 states a specific verb ('Run') and resource ('evidence-backed digital gap report on a target company website'), which clearly distinguishes it from sibling tools like ni_order_status or ni_bridgeai_run. It immediately communicates what the tool accomplishes.

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 description provides clear context for when to use the tool: when a digital gap report on a target domain is needed. It also gives a direct follow-up instruction to call ni_order_status after payment, which guides the agent through the expected workflow. It does not explicitly list when not to use it or compare against alternative gap-report tools, but the context is strong enough for correct selection.

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