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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the bar is lower; the description still adds real value by stating the call is free and defining dailyCap as a rolling 24-hour API credit cap with used/limit/resetsAt. It does not cover rate limiting or freshness of the balance, but those are minor against an already-safe read tool.

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 sentence front-loads the returned fields, parenthetically defines the one non-obvious field, then closes with the cost and timing advice. No filler and nothing buried.

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 carries the burden of describing returns and does so for all four top-level items, including the nested dailyCap shape. "Shop metadata" remains an unenumerated catch-all, which is the only real gap for such a low-complexity tool.

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?

There are zero parameters and the schema is empty with additionalProperties=false, so there is nothing for the description to disambiguate. It implicitly confirms the call takes no arguments by scoping everything to "this API key".

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 names the resource (this API key's account) and enumerates exactly what is returned: shop metadata, plan, credit balance, and the dailyCap object. That is clearly distinct from get_job, create_photoshoot_batch, list_options, and wait_for_job, though it never explicitly contrasts itself with any of them.

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?

"Free; call before spending credits" gives an explicit call condition tied to credit budgeting, which is actionable guidance rather than vague context. It stops short of naming alternatives or stating when not to call, but for a zero-parameter, side-effect-free lookup the practical guidance is sufficient.

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