Get account and credit balance

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: credits reset on the 1st of each calendar month, usage past the limit is billed as overage, and the free tier consumes no credits — context an agent needs to interpret the numbers correctly.

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?

Two sentences, front-loaded with the verb+resource, with each trailing clause (reset date, overage billing, free-tier exemption) carrying distinct semantic weight. No filler.

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?

There is no output schema, so the description must convey return contents — and it does, listing the four values returned. The billing-cycle and overage notes make the returned numbers interpretable; only the cross-tool relationship to get_usage_stats is left open.

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 is 4. The description introduces no parameter concepts and correctly needs none.

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?

Names the resource (EzVerify account info) and enumerates exactly what comes back: plan, credits used, credits remaining, monthly limit. It's clearly a read of account/credit state, but it never contrasts itself with the sibling get_usage_stats, which an agent could plausibly confuse with this.

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?

Usage is only implied — an agent infers 'call this to check plan or credit balance.' There is no explicit when-to-use/when-not, and no pointer telling the agent to prefer get_usage_stats for usage history versus this for balance.

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