Get the account summary

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds the important scoping trait that data is limited to the API key's organization plus the time horizon of the series (30 days). It does not say whether figures are live or cached, what units/currencies they use, or how webhook health is expressed.

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?

One sentence, front-loaded with the scope ('API key's organization') followed by the content inventory. Every element 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?

With no output schema, the description is the only source of return-value information, and it only names categories rather than structure, keys, or units. It is enough to decide to call it, but thin for interpreting results.

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 no parameters, so there is nothing for the description to document beyond the fixed scope; stating that the summary is scoped to the API key's organization is a useful implicit account of why no inputs exist.

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 clear resource and enumerates its contents (payment totals, settled volume, webhook health, 30-day series), which distinguishes it from record-level siblings like get_payment and get_balances. It lacks an explicit verb but 'Overview of the API key's organization' effectively conveys the aggregate read.

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?

No statement of when to use this versus list_payments or get_balances, and no prerequisites or exclusions. The word 'Overview' only weakly implies it is a starting-point/dashboard call.

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