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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description only adds that it is retrospective activity over a bounded lookback window, with no mention of what gets aggregated or whether results are paginated — modest value over the structured fields.

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 padding; the time-window constraint is stated up front. It is efficient, though so terse that it omits information an agent needs, which is penalized elsewhere.

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?

Three parameters at 0% schema coverage, no output schema, and no nested objects. The description should at least hint at the return shape (counts, activity summary) and the roles of projectId/siteId, since nothing else documents them; it does neither.

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, and it only explains rangeDays ('the last 7, 30, or 90 days'). The two required parameters, projectId and siteId, are left entirely unexplained in both schema and description.

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 concrete verb-resource pair: reading the retrospective activity of the outreach agent. An agent can tell this is a summary/reporting tool rather than a mutation, but the description never says 'overview' or how it differs from close siblings like get_outreach_sending_dashboard, list_outreach_automation_runs, or get_outreach_automation_policy.

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 when-to-use, when-not-to-use, or alternative is named. The time windows (7/30/90 days) hint at a retrospective-analysis context, but nothing tells the agent whether to reach for this instead of the runs list or the sending dashboard.

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