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

Beyond the annotations, the description discloses the return decision values, exception-only output, per-step baseline, stop condition when the registry page does not name the vendor, refund behavior for unexecuted steps, and the x402 price. These are meaningful operational traits that an agent could not infer from readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false alone.

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?

The description is front-loaded with the core purpose and then adds return, opt-in, stop, refund, and pricing details without excessive padding. It is dense but organized, though the skip_deep_vetting reference adds avoidable confusion.

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?

For a complex bundle with only one input parameter and no output schema, the description does well to explain the decision return and exception output. However, it leaves the invocation semantics of task unexplained and mentions optional controls that are absent from the schema, so an agent cannot confidently construct a complete call from this definition alone.

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?

The schema has only one parameter, task, with 100% description coverage, but the description never explains what vendor details or query text should go into task. Worse, it references skip_deep_vetting=false even though no such parameter exists in the schema, which can cause an agent to attempt an invalid argument.

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 bundle action: vendor onboarding with registry check, trust record, DD scan, optional sanctions screen, and near-duplicate check. It is clear what the tool does, though it does not explicitly distinguish itself from the similar sibling procurement.vendor-vetting or the due-diligence bundles.

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?

Usage is implied by 'Vendor onboarding' and the description notes that deep vetting is opt-in, but it gives no explicit when-to-use versus when-not guidance. It never names procurement.vendor-vetting, bundle.due-diligence, or another alternative, so routing still requires inference.

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