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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that — that spend is measured in UTC and that the response includes cap, spent, and remaining — but says nothing about scope (whose connection is returned) or freshness of the numbers.

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?

It is short, but it is structured as a colon-led list of return fields rather than a front-loaded statement of purpose. A leading verb clause would have cost the same length and made the intent immediately scannable.

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 enumeration of return content (project scope mode, daily cap, spend today UTC, remaining) does real work and is the description's main value. However, it never states that this returns the current authenticated connection with no parameters, nor how project-scope modes affect the numbers, leaving the agent to infer the read semantics entirely.

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. Baseline 4 applies; no parameter gaps exist.

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 is a noun-phrase fragment ('This connection: ...') that enumerates returned fields rather than stating an action, so the verb must be inferred from the name/title. It identifies the resource as the caller's connection but does not distinguish it from siblings like get_account, get_credits, or get_usage_today.

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?

There is no guidance on when to call this versus the closely overlapping siblings get_credits and get_usage_today, which appear to cover credit caps and daily spend respectively. No prerequisites or exclusions are stated.

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