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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side-effect profile are fully covered without the description. The text adds the returned data categories and the quota-checking rationale, which is genuinely useful, but says nothing about auth/scopes failure modes or whether credits reflect pre- or post-reservation state.

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: the first enumerates outputs, the second gives the operational cue. Nothing is redundant and the highest-value information is front-loaded.

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 four response areas, which is enough for an agent to know what it will get. Minor gap: it does not say what happens when no workspace is connected or how scopes are represented, which matters because scopes gate the other tools.

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 and the schema is an empty closed object, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 ("Read") plus an enumerated resource set: workspace, credits, concurrency limits, granted scopes. That content list lets an agent distinguish it from the sibling get_* tools, which all return job/workflow/file objects rather than account-level state. Slight ambiguity in "connected workspace", which could be misread as project data, keeps it off a 5.

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?

"Check before planning paid work" is an explicit usage trigger tied to a concrete condition (paid/quota-consuming operations), which is exactly the decision an agent faces given siblings like quote_job and submit_job. No exclusion clause or named alternative is needed here since no sibling duplicates account lookup.

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