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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and side-effect profile are covered. The description's added value is disclosing the composed response contents and the comparison window ('this month vs last month'), which an agent cannot infer from the empty schema; it does not mention currency, timezone, or whether figures are gross or net.

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 sentence, front-loaded with the purpose and then the metric list, with no filler or restatement of the title. Every clause corresponds to something the caller will receive.

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 input parameters and no output schema, the description carries the full burden of explaining what comes back, and it does so by naming each metric and the month-over-month comparison. Nothing an agent needs in order to decide to call it and interpret the result is missing at this level of granularity.

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 zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The enumerated metrics are return content rather than inputs, so no parameter meaning is missing.

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 verb ('Get') and resource ('business overview') and then enumerates the exact contents: invoice totals, month-over-month revenue, outstanding balance, new customers, overdue invoices, and status breakdown. This makes the composite/dashboard nature clear enough to distinguish it from single-metric siblings like get_revenue_report or get_invoice_aging, though it never explicitly says it aggregates what those tools report individually.

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 word 'quick' implies a fast summary use case versus the detailed sibling reports, which is a reasonable implied signal. However, there is no explicit when-to-use statement, no exclusions, and no named alternative for when the agent needs deeper per-invoice or per-customer detail.

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