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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds valuable context beyond annotations: it is free and unmetered, the balance includes test credit, and it names the related topup endpoint. Minor gap: it does not describe caching, freshness, or error behavior.

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 with zero waste. The first front-loads the returned data; the second covers cost model and the follow-up topup endpoint. Every clause earns its place.

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 read tool with annotations covering safety, the description is nearly complete: it explains the return payload, cost model, and the topup alternative. There is no output schema, so return fields must be inferred from prose, but the prose enumerates them adequately.

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?

Zero parameters, so the baseline is 4. The description correctly implies no input is needed and adds semantic value by explaining what the returned fields mean (cents, test credit, daily cap, licenses) even though no output schema exists.

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 resource (photo wallet) and enumerates exactly what it returns: balance in US cents, test credit, today's spend against the daily cap, and held licenses. The agent knows precisely what data comes back, distinguishing it from siblings like num_license_photo or num_quote_photo.

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?

Mentions it is free and unmetered and routes to the topup endpoint for adding credit, giving clear when-to-use context. It does not explicitly contrast with sibling tools like num_quote_photo or num_license_photo, so the differentiation is implicit rather than stated.

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