Get Subscription Status

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, so the safety profile is clear. The description adds a detailed return structure, including fields like subscription status and plan details, which provides useful behavioral context beyond annotations.

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 concise: two sentences. The first states the purpose, and the second specifies no arguments and shows the return shape. Every sentence contributes value without waste.

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?

Given the tool has no parameters and rich annotations, the description is fairly complete. It provides the return structure (missing an output schema). However, it does not differentiate usage from sibling tools like 'influIQ_list_plans' or 'influIQ_get_credits_balance', which slightly reduces completeness.

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?

There are zero parameters, and the input schema is empty with 100% coverage. The description correctly notes 'No arguments required.' According to the guidelines, 0 parameters gives a baseline of 4, and no additional parameter semantics are needed.

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 explicitly states 'Get your current subscription plan, status, usage, and billing period.' It uses a specific verb and resource, and clearly distinguishes from sibling tools like 'influIQ_list_plans' which lists available plans, and 'influIQ_auth_status' which checks authentication.

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 lacks any guidance on when to use this tool versus alternatives. It states 'No arguments required' but does not provide context on when not to use it or mention specific use cases. No exclusions or alternatives are discussed.

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