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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds nothing behavioral beyond those annotations — no mention of what the check evaluates, whether it hits a billing provider, latency, or failure modes.

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?

It is short but wasteful: the identical endpoint string is duplicated verbatim, adding zero information. The content is under-specified rather than concise, so the brevity reflects a lack of substance.

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 two undocumented parameters, no output schema, and an abstract nested query object, an agent cannot know what to pass or expect. The description does not fill this gap, leaving the definition incomplete for invocation.

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 coverage is 0% for two parameters (query and params), and the description does not explain what either accepts. Its only help is deferring to describe_operation, which is a pointer rather than actual parameter semantics, so it fails to compensate for the coverage gap.

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 merely repeats the HTTP path 'GET /api/subscription/billing-check' twice and gives an opaque operation ID. It never states in plain language what a billing check does or what it returns, so the agent must infer purpose from the endpoint name alone. This is essentially a tautology of the tool title.

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 indication of when to call this versus siblings such as get_subscription_status, get_subscription_trial_status, or get_subscription_usage_summary. The only directional hint is that describe_operation 'provides native request schemas', which is a pointer to another tool, not usage guidance.

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