Get remaining Verifly credits

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral trait by stating 'Costs no credits' and clearly lists the data returned (today/this month usage, plan). This exceeds minimal transparency, though it omits details like data freshness or authentication.

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 short sentences, front-loaded with the primary action and result, and includes an important cost note. Every word earns its place with no filler or repetition.

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 zero-parameter tool with no output schema or annotations, the description is remarkably complete: it specifies exactly what data is returned (remaining credits, today's/monthly usage, plan) and the cost behavior. It provides all necessary context for an agent to invoke this tool confidently.

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 takes zero parameters, so the baseline for this dimension is 4. The description adds meaning by explaining the return values, which is essential given there is no output schema. It does not need to explain parameters that do not exist.

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 returns remaining verification credits, recent usage, and plan. The verb 'Return' and specific resource (API key's remaining verification credits) make the purpose unambiguous, though it doesn't explicitly differentiate from sibling tool get_usage.

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 usage for checking credit status without cost, but it does not explicitly state when to use this tool versus others like get_usage or get_account. The 'Costs no credits' note is a contextual hint but not full guidance.

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