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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description's only added content is a pointer that describe_operation holds native request schemas, which is mildly useful routing but discloses nothing about what data is returned or how usage is aggregated.

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 text is short only because it is a duplicated URL string with no front-loaded explanation of the operation; the repetition is noise rather than concision.

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?

For a tool with a nested free-form query object, zero parameter documentation, and no output schema, the description provides no information about what the usage summary returns or how to shape the request. An agent cannot invoke it correctly from this definition alone.

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 0% on two parameters, and the free-form 'query' object with additionalProperties is completely undocumented. The description supplies no parameter meaning whatsoever, leaving the agent unable to know what query keys are valid.

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 is nothing but the endpoint path repeated twice plus an operation ID; the only signal of purpose comes from parsing the URL itself, which merely restates the tool name and title rather than describing what the summary contains.

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 guidance on when to call this versus siblings like get_subscription_ai_usage, get_subscription_ai_token_cost, or get_subscription_status, nor any conditions, prerequisites, or exclusions.

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