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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context the annotations do not: this call requires a subscription API key in the 'sff_...' format. It stops short of describing error behavior for a missing/invalid key, so not a 5.

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, no filler. The high-value content (what you get back) is front-loaded and the credential prerequisite is placed second, which is the correct ordering.

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 parameters and no output schema, the description does the necessary work by naming the three returned data groups, and it covers the auth prerequisite. It could go slightly further by noting what a failed auth returns or the response shape, but for a trivial read tool this is close to complete.

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 per the baseline there is nothing for the description to disambiguate and a 4 is the ceiling. The description's mention of the API key is an auth requirement rather than a schema parameter, so it adds no parameter-level semantics.

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 (Get) plus resource (account/subscription info), and it enumerates exactly what is returned: plan details, remaining fax quota, billing period. That is well beyond a restatement of the name. It doesn't explicitly position itself against siblings, though the account/subscription domain is naturally distinct from the fax-operation siblings (send_fax, list_fax_history, etc.).

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?

The description implies the obvious use case (checking your plan/quota) and states the prerequisite credential, but gives no explicit when-to-use vs when-not guidance and never names an alternative. For a simple zero-arg read tool, implied usage is arguably sufficient, so a 3 rather than a 2.

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