Get account

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that, the description discloses the returned data (credit balance and today's remaining solves), which is meaningful behavioral context, and the phrase "left today" hints at a daily-resetting quota. It stops short of stating whether the quota resets on a fixed schedule or requires authentication details.

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?

A single front-loaded sentence with no filler, listing the two payoff fields immediately. Nothing is repeated from the title or schema.

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 no output schema, the description usefully summarizes the returned fields, which is what an agent most needs here. Minor gaps remain — no mention of plan name, currency, or quota reset timing — but for a simple read-only lookup this is close to sufficient.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument call scoped to the calling account.

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?

States a specific verb and resource (get account) and enumerates what it returns: credit balance and remaining solves for today. This clearly separates it from siblings like solve_hcaptcha, cancel_solve and list_solves, which operate on individual solves. The odd string "NoneCap" reads like an unfilled placeholder and slightly muddies the name of the service.

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 implied: call it to check credits or how many solves remain today. There is no explicit when-to-use/when-not guidance and no mention of alternatives, though for a zero-parameter account lookup the implied usage is fairly unambiguous.

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