get_billing_status

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered without the description. The description's real contribution is naming the required `billing:read` scope, which is genuine auth context an agent needs before calling. It stops there, adding nothing about what the response contains for a tool with no output schema.

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 short sentences with no filler, and the purpose statement is front-loaded ahead of the scope requirement. The brevity is honest rather than padded, though it edges toward under-specification rather than efficiency.

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 full annotation coverage, the description covers the invocation prerequisites (scope) but not the payload: an agent cannot tell whether this returns a plan tier, seat counts, renewal date, or payment state, and there is no output schema to fall back on. It is minimally sufficient to call, not sufficient to use the result.

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 and the schema-object baseline of 4 applies. No parameter-level 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 phrase 'Plan and subscription status' is essentially a restatement of the tool's own title and name, with no verb to anchor the action. It does narrow 'billing status' to plan/subscription data, which is slightly more concrete than the identifier alone, but it does not distinguish this from billing-adjacent siblings like get_usage or get_referral_stats.

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 statement of when to call this versus get_usage, list_member_usage, or get_referral_stats, all of which sit in the same billing/account space. The only implied guidance is the scope requirement, which is a precondition rather than a usage rule.

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