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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's 'Read-only' simply repeats that. The genuinely additive parts are the credential requirement (account-wide key) and the plan gating (Agency/Enterprise), which an agent needs before invoking and cannot get from annotations. No return format or freshness detail is given, but the auth/plan context carries real weight.

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?

The content is dense and front-loaded: returned fields first, then eligibility/credential constraints, with almost no filler. The stray trailing token '[#bf5472]' is noise that should not be in the definition, which keeps it from a perfect score.

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 present, the description correctly compensates by enumerating the returned fields, and it states plan eligibility and key scope. It is complete enough to call the tool safely, though it omits any note on how seat figures are scoped or whether the agency flag can be absent.

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 is 4. The description instead spends its space describing outputs (account name, role, agency flag, seat counts), which is appropriate and adds no conflicting parameter information.

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 enumerates exactly what the tool returns at account level: account name, caller's role, agency-feature flag, and seat accounting (used/included/billable). That is specific and distinguishes it from account-adjacent siblings like list_account_members or get_role_matrix, though it never states an explicit verb such as 'retrieve'.

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?

It supplies applicability context ('Agency / Enterprise; needs an account-wide key'), which tells an agent the plan tier and credential scope required. However, it names no alternatives and gives no when-not-to-use condition against the many sibling account/settings tools, so usage is implied rather than directed.

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