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

Annotations only declare readOnlyHint=true; the description adds the required permission scope (billing.read) and, more importantly, discloses what the payload contains - the applicable ladder, whether it is enforced or still shadowed, the remedy copy, and the paused actions. The trailing 'Read-only.' restates the annotation, which is minor redundancy rather than contradiction.

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?

Front-loads the payload contract in the first clause, then the trigger condition, then the permission. The em-dash chain and the CLI-twin parenthetical add density, but each element carries information an agent needs to decide whether to call it.

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?

No output schema exists, and the description compensates by spelling out the returned facets in order. Combined with the permission requirement and the trigger conditions, an agent has everything needed to select and call it without further context.

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?

Zero parameters, so the baseline is 4; there is no schema surface for the description to clarify. The description instead scopes the read to 'the organisation's' standing, which implicitly fixes the subject of the implicit query.

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 resource (the organisation's billing standing) and enumerates exactly what it resolves: which ladder applies (overdue invoice, credit limit, exhausted prepaid wallet, free-tier capacity), enforcement vs shadow, remedy copy, and paused actions. It also self-identifies as the read model behind `ankra org billing standing`, which separates it from neighbouring cost/wallet reads like get_wallet_balance.

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?

Gives two concrete triggers: an action refused with a payment-required error, or a user asking why growth is paused. That is strong positive routing. It stops short of naming alternatives (e.g. get_wallet_balance or get_usage) or stating when this is the wrong tool, so it is clear context without exclusions.

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