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

Annotations already establish that this is a safe read operation, so the description only needs to add context. It adds that the tool reports outreach-agent activity over a time window, but it does not describe aggregation level, return contents, or how the stated 7/30/90-day windows relate to the schema's from/to parameters.

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 front-loaded sentence with no wasted wording. It is appropriately sized for the information it chooses to convey.

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?

For a tool with four parameters at 0% schema description coverage and no output schema, the description is too thin. It does not clarify required identifiers, how date range selection works, or what an 'overview' returns, so an agent could easily invoke it with incorrect assumptions.

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%, so the description must compensate, but it only mentions 7, 30, or 90 days while the schema exposes arbitrary from/to date-time fields. It also does not explain the required siteId and projectId parameters, leaving most parameter semantics undocumented.

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 states a specific verb and resource: reading what the outreach agent did, with a temporal scope. It is clearer than a tautology, but it does not explicitly differentiate this overview from siblings like list_outreach_automation_runs or get_outreach_sending_dashboard.

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?

It gives no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The time ranges imply a reporting use case, but the agent is left to infer when this overview is appropriate.

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