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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds essentially nothing beyond that: it does not say whether results cover sent campaigns only, how per-variant results are aggregated, or whether data is live, leaving the agent with just the bare operation.

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 front-loaded sentence with no filler; however, its brevity reflects under-specification rather than disciplined conciseness.

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 should indicate what 'performance' means — open rate, click rate, sample size, per-subject-line breakdown. None of that is present, so an agent cannot anticipate the return shape or judge whether this tool answers its question.

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 0% for the single campaign_id parameter, so the description carries the burden and fails it — 'your campaign' only loosely gestures at campaign_id without stating format, valid range, or where to obtain the id (e.g., from list_campaigns).

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 ('Read') and resource ('subject line performance'), which is meaningfully narrower than generic siblings like get_campaign or get_campaign_audit. It does not explicitly name the sibling it differs from, so an agent must infer that subject-line-specific metrics are unique to this tool.

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?

No guidance on when to call this versus get_campaign, get_campaign_drafts, or get_campaign_audit, all of which touch campaign data. No prerequisites or conditions (e.g., campaign must have sent a test) are stated.

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