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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond them: it discloses what is deliberately NOT returned (payment method details, truncated Stripe customer id) and conditional null semantics for monthlyPosts and dailyPosts, which prevents misinterpretation of missing values.

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 sentence with zero filler, and the most important item (subscription status) is front-loaded. The enumeration of fields is dense but each item earns its place by documenting an otherwise undisclosed return value; minor cost is readability of a long run-on list.

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 and no parameters, the description carries the full burden of describing the response, and it does so by enumerating the returned fields plus two key caveats (redaction, nullable caps). It stops short of describing the shape of the billing-events list or units/currency, which would fully close the gap.

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 the baseline is 4; there is nothing for the description to clarify about inputs. The text instead spends its budget on output field semantics, which is the right allocation for a parameterless tool.

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 field list makes clear this returns subscription/billing state (status, plan, period end, handles, caps, recent billing events), which is concretely distinguishable from analytics or audience tools. However, it never explicitly contrasts itself with the close sibling sprkly_get_account_summary, so an agent must infer the boundary between 'billing' and 'account' summaries.

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 when-to-use guidance, no statement of exclusions (e.g. 'use get_account_summary for profile/plan usage'), and no prerequisites. The only implicit signal is that it is billing-related, which the agent would have guessed from the name alone.

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