didit_vendor_business_create

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

The description adds minimal behavioral context beyond annotations. It declares it is a 'Create' operation, consistent with readOnlyHint=false. However, it does not disclose side effects, idempotency, permission requirements, or any validation behavior that would help an agent anticipate tool behavior.

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 extremely short (5 words), which is concise but at the cost of informativeness. It conveys the basic purpose but does not earn its place for a tool with 7 parameters and low schema coverage.

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 the tool's complexity (7 parameters, nested objects, output schema), the description is incomplete. It does not explain parameter roles, output format, or prerequisites. The context 'manual KYB' is helpful but insufficient for full understanding.

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 description does not mention any of the 7 parameters despite low schema description coverage (29%). It fails to add meaning beyond what the schema provides. Parameters like 'vendor_data' or 'country_code' are critical but undocumented in the 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 'Create a business record manually (KYB)' uses a specific verb ('Create') and resource ('business record'), and adds context about the method ('manually') and purpose ('KYB'). This clearly distinguishes it from sibling tools like 'didit_vendor_business_update' or 'didit_vendor_business_delete'.

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 implies use for manually creating a KYB business record, but provides no explicit guidance on when to use this tool versus alternatives (e.g., automated creation, or updating existing records). No when-not-to-use or exclusion criteria are given.

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