Get the authenticated account's monthly verification quota: plan, used, limit, and remaining. Call this before verify_photo to check the free-tier allowance.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It mentions 'authenticated account' and describes a read-only quota check, which implies no side effects. However, it doesn't explicitly state that the operation is non-destructive or doesn't consume quota, but the verb 'Get' and the context is sufficient for a simple reader.
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 two sentences, front-loaded with the purpose, and every word earns its place. It includes the key data fields and the usage context without any redundancy.
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?
With an output schema present, the description doesn't need to explain return values. It covers the tool's purpose, the data it returns, and when to call it, making it complete for a simple read-only tool with no parameters.
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 tool has zero parameters, so the schema provides complete coverage. With 0 params, the baseline is 4 per instructions, and the description adds no unnecessary parameter information, making it appropriate.
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 gets the authenticated account's monthly verification quota, listing specific fields (plan, used, limit, remaining). It uses a specific verb 'Get' and resource, differentiating it from sibling verification tools that perform actions on individual verification items.
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?
It explicitly instructs to call this tool before verify_photo to check the free-tier allowance, providing a concrete use case and naming an alternative tool. This gives clear when-to-use guidance, even though it doesn't list exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action and resource: uploads, account usage, listings, verifications, sharing, and the two verification methods are clearly differentiated by input type (single image vs RAW+JPEG). The get_verification and get_verification_share pair is unambiguous due to specific descriptions.
All tool names use lowercase snake_case with a verb_noun pattern (create, get, list, share, unshare, verify), making the set predictable and consistent. Even longer names like verify_content_credentials follow the same verb-first convention.
With 11 tools, the server covers uploads, verification, results retrieval, sharing, account usage, and marketplace listing retrieval without redundancy. This is a well-scoped count for the feature set.
The verification lifecycle is well covered: create (two methods), upload, get, list, share/unshare, and usage check. The only notable gap is that marketplace listing management is read-only (no create/update/delete), but that's tangential to the core verification purpose.
