didit_vendor_business_list

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

Annotations already declare readOnlyHint true and destructiveHint false, so the tool is safe. The description adds behavioral context: grouping by vendor_data, scope behavior, and pagination support. No contradictions. Does not mention auth or rate limits, but annotations cover safety.

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 sentences, no wasted words. Front-loaded with main purpose, then guidance, then pagination details. Every sentence adds value.

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 list tool with output schema and pagination, the description covers all essential aspects: what it lists, scope behavior, pagination, and alternative tool. No gaps.

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 0%, so description carries the burden. It states 'Supports limit/offset pagination', clarifying the purpose of the two parameters. While it doesn't specify format (e.g., integer strings), this is sufficient for a list tool.

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 clearly states it lists verified businesses (KYB, grouped by vendor_data) for one app or auto-spans across apps. It distinguishes from sibling didit_vendor_business_search by specifying 'cross-app lookup prefer ...'. The verb 'List' and resource 'verified businesses' are specific.

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?

Explicitly advises to use didit_vendor_business_search for cross-app lookups, providing a clear alternative. Also implies this tool is for single-app or auto-spanning contexts, giving practical usage context.

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