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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description does not need to re-establish safety. It still adds real value by clarifying that checking the balance 'consumes nothing' — non-obvious for a credit-metering tool — and by noting that DAW conversions draw from the monthly pool, which explains the meaning of the numbers returned.

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 tight sentences: the first front-loads what the tool returns, the second states the safety property and the recommended usage point. Every clause carries information and nothing is repeated from the schema or annotations verbatim.

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 compensates by naming the four categories of data returned, which is what an agent needs to decide whether to call it. It stops short of describing the response shape or units, but for a trivial zero-parameter read that is a minor gap.

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; the baseline for a zero-parameter tool applies. No misleading parameter-like language is introduced.

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 ('Check the connected doseedo account') and enumerates exactly what it reports: plan tier, monthly credit pool, purchased extra-usage credits, and storage. All siblings operate on sessions, jobs, or uploads, so this is unmistakably the account-inspection tool.

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?

Gives a concrete trigger: 'Use it before a batch of conversions to confirm there is budget.' That tells the agent where in a workflow to call it. It does not name an alternative or state a when-not-to-use case, but no sibling overlaps this function.

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