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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: Site Growth gating for scans and community search, and the fact that when inactive the dashboard explains why (plan limitation or unpublished site). It does not describe response shape or freshness/pagination, but the added behavioral context is substantive.

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?

Front-loaded with the overview statement, followed by a dense but purpose-built enumeration and a single routing sentence. The middle list is long, yet each clause maps to a distinct piece of dashboard content, so little is wasted; a bulleted grouping of status vs. counts vs. activity would read slightly better.

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?

There is no output schema, and the description compensates by enumerating the return contents — including the diagnostic 'why Site Growth is inactive' case that an agent would otherwise miss. Combined with a rich annotation set on a simple read-only tool, an agent has everything needed to call 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% — site_id is documented as coming from list_sites and user_goal has its own explanation — so the schema does the heavy lifting. The description adds no parameter-level detail such as site_id lookup or what user_goal influences. Baseline 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?

Opens with a precise framing ('The site's marketing overview') and then enumerates exactly what it returns — Site Growth active state and why-not reasons, onboarding status, opportunity counts, idea progress, content-idea counts, last scan date, recent activity. This is clearly distinguishable from siblings like list_growth_opportunities or list_growth_content_ideas, which return the detailed lists rather than the aggregate view.

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?

'Call it first when the user asks how their marketing is going' gives an explicit trigger, and 'scans and community search need it' documents a prerequisite for other tools. It stops short of naming an alternative or an exclusion case (e.g. when to go straight to list_growth_opportunities), so it is strong but not exhaustive routing guidance.

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