wave_get_subscription

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

The description states 'GET' and 'Get', which implies a read-only, non-mutating operation. However, with no annotations provided, it does not disclose authentication requirements, possible absence of a billing account, or error behavior, so the behavioral transparency is only partially covered.

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, well-structured sentence that leads with the action and resource, then gives the endpoint and expected data. Every element is useful and there is no redundancy.

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 zero-parameter read-only tool with no output schema, the description adequately conveys what the call returns. It could be more complete by noting whether the billing account may be absent or require setup, but for simple invocation context it is largely sufficient.

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 has zero parameters and the schema is empty, so there is nothing to document. The description adds value by indicating the fields the response contains, helping the agent understand what the tool returns.

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 names a specific verb and resource ('Get the current billing account') and enumerates what it returns: plan, Stripe customer status, and subscription state. This clearly separates it from siblings like wave_get_usage or wave_get_viewers, which cover different domains.

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 makes the use case clear: an agent should call this tool when it needs billing or subscription details for the current account. It does not explicitly exclude alternative tools, but the billing-specific resource and returned fields make the appropriate context evident.

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