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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations by enumerating what data the summary includes and noting that exceeding the monthly event limit pauses ingestion.

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?

The description is a single, front-loaded sentence that leads with the main purpose and then lists the included information. The length is justified by the richness of the summary, though it could be broken into a list for easier scanning.

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 must explain the return value. It does so comprehensively, covering the customer, user, roles, billing plan, limits, subscription status, dates, current usage, exceeded flag, and dashboardUrl. This is sufficient for an agent to know what to expect from the call.

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 input schema has zero parameters, so the schema itself is trivially complete and no parameter documentation is needed. The baseline of 4 applies; the description adds nothing about parameters because none 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?

The description uses an explicit verb ('Describe') tied to a specific resource ('the account this connection acts in') and enumerates the contained fields (customer, user, roles, billing plan, limits, usage). This clearly differentiates it from sibling get_* tools that target channels, identities, or rules.

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 does not explicitly state when to use this tool versus any alternative, nor does it name exclusions. The usage is implied by the resource it describes—an account-level summary—and there are no comparable siblings, but the guidance is left to inference.

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