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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses exactly what is returned and the non-obvious aggregation rule 'Usage is summed across all partitions,' which prevents an agent from misreading per-partition 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?

Two sentences, both load-bearing: the first front-loads the returned payload, the second front-loads the use case. No filler, no restatement of the tool name, and the aggregation caveat is placed immediately after the data inventory it qualifies.

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 describing return values — and it does, listing org identity, home partition, plan limits (sites, domains, storage, bandwidth), and usage counts. For a zero-argument read tool with annotations covering safety, nothing an agent needs is missing.

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?

Schema description coverage is 100%, and both parameters (`llm_model`, `conversation_id`) are thoroughly documented in the schema itself, including the analytics-only purpose and the conversation_id chaining rule. The description adds nothing about parameters, so the baseline 3 applies; the tool exposes no business parameters to explain.

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?

Specific verb-plus-resource ('Get the user's account') followed by an enumeration of the returned data: org details (`orgId`, `orgName`), `user.homePartition`, subscription plan limits, and usage counts. This clearly separates it from the site/domain/deploy siblings, which operate on resources rather than account metadata.

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?

Explicitly states when to reach for it: 'to check how much headroom the user has before creating new sites or to confirm plan-tier features.' It gives concrete intent without naming an alternative tool or a when-not-to-use condition, so it stops just short of a 5.

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