insumer_request_domain_verification

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

No annotations are provided, so the description carries the burden. It reveals that the tool returns 'the token and three verification methods,' and that 'Verified merchants get a trust badge.' It also notes the permission requirement ('Owner only'). These add behavioral context beyond the 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?

The description is concise at 4 sentences, each adding value: purpose, return details, next step, benefit, and permission. No wasted words, well structured.

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?

The description covers return values, next steps, and usage context. Even without an output schema, it provides enough information for an agent to understand and use the tool correctly. It also mentions the benefit (trust badge) and permission, making it contextually complete.

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%, so baseline is 3. The description does not add additional meaning to parameters beyond the schema. It mentions 'domain' and 'merchant' implicitly but no extra details.

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 the tool's purpose: 'Request a domain verification token for a merchant.' It specifies the resource (domain verification token) and action (request). It also distinguishes from the sibling tool 'insumer_verify_domain' by explaining this is the first step before verification.

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 explicit guidance: 'After placing the token, call insumer_verify_domain to complete verification.' This tells the agent when to use the sibling tool. It also mentions 'Owner only,' indicating who can use it. However, it lacks explicit when-not-to-use or alternative scenarios.

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