verify_phone_three

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

No annotations provided, but description covers return content (match result, carrier info, phone region, status) and mentions free tier limit. Could add error handling details, but current info is sufficient.

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 purpose and key information. Each 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?

No output schema, but description explains what fields are returned. For a verification tool, this is fairly complete, though output format details are missing.

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% with detailed descriptions, min/max lengths, and examples. Description adds no additional parameter meaning beyond what schema provides, so baseline 3 applies.

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?

Description clearly states the tool verifies if a person's name, ID card number, and phone number match. The specific verb 'verify' and resource 'phone three elements' distinguishes it from siblings like verify_identity or verify_bank_card.

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?

Provides explicit use cases: phone number ownership verification, telecom fraud prevention, user registration validation. No when-not or alternatives, but context is clear from the use cases and sibling names.

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