admin_get_subscription_status

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

With no annotations, the description must disclose behavioral traits. It correctly identifies the tool as a retrieval operation, but does not explicitly state that it is read-only or require authentication, leaving some uncertainty for the agent.

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 description is a single sentence, front-loading the verb and key nouns with zero extraneous words—every word earns its place.

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 parameter-less tool with no output schema, the description adequately conveys what the tool retrieves. However, more detail on the return format or data structure would enhance completeness if output schema were 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 input schema has no parameters (coverage 100%), so the description adds meaning by listing the retrieved fields (status, trial eligibility, cancellation schedule), exceeding the baseline of 3 for high schema coverage.

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 uses a specific verb ('get') and resource ('subscription status, trial eligibility, cancellation schedule'), clearly distinguishing it from sibling tools like 'admin_get_accounts' or 'admin_get_limits_usage' which serve different purposes.

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 usage for checking subscription status, but it does not explicitly state when to use this tool versus alternatives (e.g., 'admin_get_limits_usage' for billing limits) nor provides any prerequisite or exclusion context.

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