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

The annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds that it is 'lighter and faster' but does not disclose any additional behavioral traits such as data freshness, pagination, or scoping constraints. With the annotation covering the safety profile, the description adds minimal value.

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 sentence comprising two clauses, providing all essential information without redundancy. It is front-loaded with 'Quick business overview' and includes specific metrics. Every word 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?

Given that the tool has an output schema (not shown), the description does not need to explain return values. It sufficiently lists the metrics returned (total leads, quotes, jobs, revenue, leads this week, chart data) and notes performance characteristics. For a simple dashboard tool with one optional parameter, this is 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% for the single parameter 'days', with full details in the schema. The description does not add any additional meaning or context to the parameter beyond what the schema provides. Baseline score of 3 is appropriate.

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?

Description clearly states it provides a 'Quick business overview' listing specific metrics (total leads, quotes, jobs, revenue, leads this week, chart data). It distinguishes from sibling tools like analytics.detailed and analytics.financials by noting it is 'Lighter and faster than full analytics.' This makes the purpose unmistakable.

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?

Description implies this tool is for a quick, lightweight overview, contrasting with 'full analytics.' However, it does not explicitly state when to avoid this tool or name alternatives, though the sibling tool names provide context. Still, the guidance is clear enough for an agent to infer appropriate use.

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