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

Annotations already declare the safe-read profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description adds real content: it enumerates what comes back (org, auth method, scopes, credit balance broken into available/monthly/top-ups). With no output schema, this return-shape disclosure is genuinely useful; it just omits edge behavior such as exhausted-credit or auth-failure states.

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?

Three tight sentences, front-loaded with the identity/org/balance summary before the workflow hint. No filler, though the middle sentence partially restates the first.

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 return-value burden and does so by naming the organization, auth method, scopes and credit breakdown. It is nearly complete for a zero-parameter read tool; only failure/edge semantics are left implicit.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter guidance is missing.

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 states a specific resource ('the organization the credentials act for', 'their scopes', 'the credit balance') with concrete subfields, so the agent knows exactly what this returns. It is clearly distinct from every sibling, which operate on artists, songs, videos and looks rather than account/identity.

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?

It gives an explicit when-to-use cue: 'Check it before creating videos.', which tells the agent where this fits in a workflow. It stops short of naming exclusions or alternatives, but there is no sibling that overlaps, so no route-away guidance is needed.

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