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 does add one genuinely useful behavioral fact beyond the annotations: 'Aggregates only, no customer data', which scopes what the agent can expect to retrieve. It says nothing about auth, freshness, or rate limits.

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 tightly-wrapped sentence with a parenthetical example set and a scope disclaimer; the read-only framing is front-loaded and every clause 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?

For a single-parameter, optional-argument read tool with no output schema, the description compensates well by naming the returned aggregates. Nothing essential is missing, though a pointer for when to prefer this over get_all_dashboards/weekly_recap would make it complete.

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?

Schema description coverage is 100%, and the schema already explains account_id, its type union, and that it is optional when the token is bound to a single outpost. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

Names a specific verb+resource ('aggregated KPI summary for this account') and even enumerates the payload (listing counts, 7d revenue, issue count), so the agent knows exactly what comes back. It does not, however, differentiate itself from plausible siblings like get_all_dashboards, weekly_recap, or get_account_health.

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 or when-not-to-use guidance, no mention of alternatives, and no prerequisites stated. Usage is only implicit from the word 'summary' and the sibling names.

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