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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine content beyond them by disclosing that the response is a computed rollup with specific time windows (today / last 7 days) plus live session and slot-usage counters, which tells the agent this is an aggregated snapshot rather than raw records.

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, zero filler. The first sentence names the operation and the second front-loads the most decision-relevant detail (the rollup and counters) rather than burying it.

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?

There is no output schema, so the description carries the burden of conveying return values, and it does list the major components. 'Account summary' remains unspecified, so an agent still cannot predict the full field set, but for a zero-parameter read tool the coverage is adequate.

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 the baseline of 4 applies. There is no parameter surface for the description to clarify or obscure, and the schema is trivially complete.

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 gives a clear verb+resource ('Get the authenticated account') and immediately enumerates what the payload contains (earn-side rollup, active session count, site-slot usage). It does not explicitly contrast itself with siblings like update_account or get_referrals, but the resource is unambiguous enough that an agent can separate it from the create/delete/list family.

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?

Usage is only implied: an agent infers 'call this to fetch the current account's state.' There is no explicit when-to-use statement, no mention of prerequisites (e.g. requires authentication context, which is implied by 'authenticated'), and no named alternative such as update_account for writes.

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