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 read-only nature is covered. The description adds that it returns a dashboard with specific elements but doesn't disclose details like which benchmarks or how results are computed. Given the annotations, a score of 3 is appropriate because the description adds some behavioral context but not exhaustive.

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 concise sentences: the first front-loads the purpose and expected output, the second gives a clear usage directive with an alternative. No wasted words, and the structure is optimal.

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?

This is a read-only dashboard tool with zero required parameters, full schema coverage, and rich annotations. The description sufficiently covers what the tool does and how it fits, and nothing critical is missing for an agent to invoke it correctly.

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%, with both parameters (api_key and cost_per_email) described in the schema. The description mentions 'cost per email' as part of the investment summary, linking it to the optional parameter, but doesn't add syntax or format details beyond what the schema already provides. Baseline 3 is correct.

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 states a clear verb ('Returns an at-a-glance dashboard') and resource ('portfolio-level health check across recent campaigns'), with specific components (overall grade, metric status, trends, priority action). It also distinguishes itself from analyze_latest_campaigns, making its purpose unambiguous.

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?

Explicitly says 'Use this for a fast 10-second overview; use analyze_latest_campaigns for deep analysis.' This clearly indicates when to use this tool and names the alternative for deeper work, fulfilling the when/when-not criterion.

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