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

Annotations only declare the mutation shape (readOnly=false, idempotent=false, destructive=false); the description adds what they cannot: a metered cost (one weekly scan from the plan), the refusal behavior with the next-available date, and the explicit scope statement that it contacts/posts/submits nothing. That is exactly the value-add a description should carry.

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-loads the outcome, then constraints, then the safety disclaimer — a logical order with no filler. The em-dash parentheticals make the quota sentence dense, but every clause carries information.

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 still tells the agent what is produced (directory, community, media and partnership leads plus ideas and dated content ideas) and where it lands (marketing hub), and covers prerequisites, quota, and the non-outreach guarantee. Nothing material for a correct call is missing.

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 coverage is 100% and the schema already documents site_id, the scan_type enum with 'full (default)' and user_goal. The description only restates that scan_type narrows the scan and defaults to full, adding no new semantics (e.g. what each scan_type actually returns).

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 action chain: generate marketing opportunities/ideas/content ideas and persist them to the marketing hub, plus the scan_type narrowing scope. Sibling listing tools (list_growth_opportunities, list_marketing_ideas) are implicitly contrasted by 'suggest... and save', but no sibling is named explicitly, so it stops short of a 5.

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?

Gives a clear precondition (Site Growth must be on) and points at get_growth_dashboard to check it, and warns the call consumes a plan-limited weekly scan. It never says when NOT to use it (e.g. to just read existing ideas, use list_marketing_ideas), so exclusions are missing.

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