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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), but the description adds the non-obvious access-control behavior: partners are silently scoped to their own data while admins may supply partnerId. It also anchors the default scope to the current month. It does not mention currency of revenue or whether scoping failures error out.

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?

Two compact sentences with zero filler; the metric list and the caller-role rule are both front-loaded and immediately actionable.

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 correctly compensates by listing the four returned metrics, and it covers the access-scoping nuance. Minor gaps remain around units (currency of revenue) and whether the month filter applies uniformly to all metrics.

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 coverage is 100% and the schema already documents month format/default, partnerId being admin-only, and intentId as a correlation ID. The description's mentions of current month and the admin/partner distinction restate rather than extend the schema, 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?

The description names the resource (partner dashboard) and enumerates exactly the metrics returned: label count, revenue, open tickets, unpaid invoices. A specific verb is absent and it does not explicitly distinguish itself from siblings like GetAnalytics or SummarizeUsageRecords, so it lands just below the top band.

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?

"Partners see own data; admins pass partnerId" gives a clear conditional rule for how to invoke it depending on caller role. It stops short of stating when to prefer this over GetAnalytics or SummarizeUsageRecords, so no exclusions or alternatives are offered.

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