get_subscription

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

With no annotations, the description carries the full burden, and it does disclose the content returned (tier, limits, live usage) and implies a read-only, account-scoped operation. It does not address auth/permission requirements or how 'live' the snapshot actually is (caching, freshness), which are the main behavioral unknowns for this tool.

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?

A single front-loaded sentence with the verb and resource first, followed by a compact parenthetical of plan-limit dimensions. Every clause adds identifying information, though the parenthetical is dense enough that it borders on a list dump.

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 output schema, the description does a fair job of naming the return content, and a zero-param read needs little else. However, given the crowded family of usage and billing read siblings, it leaves the agent without enough to choose this tool confidently over get_billing_plan or get_usage.

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; baseline 4 applies. The enumerated facets are all return data, not inputs, so no parameter explanation is owed.

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?

States a specific verb ('Get') and resource ('current subscription') and enumerates the returned facets: tier, plan limits, and live usage snapshot. This is clearly distinct from write tools like create_webhook, but it does not explicitly distinguish itself from overlapping read siblings such as get_billing_plan or get_usage.

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_billing_plan, get_usage, or get_usage_history, all of which plausibly overlap. Usage is only implied by 'for this account'; no exclusions or alternative routing are given.

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