generate_growth_plan

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

With no annotations provided, the description carries the full burden. It mentions 'syncs GSC, runs analysis', which gives some behavioral hint, but it does not disclose whether the operation is asynchronous, destructive, requires credentials, or what side effects occur (e.g., creating a stored plan). The description lacks critical behavioral details for a generation tool.

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 sentence with a parenthetical aside, conveying the core action and key sub-steps efficiently. Every word earns its place, with no redundancy or filler.

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?

The tool has a single parameter but performs a complex operation (sync, analysis, generation). With no output schema and no annotations, the description should at least hint at return values, duration, or side effects. The minimal details leave the agent uncertain about what to expect after invocation.

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?

The input schema already provides 100% coverage for the single parameter (site_id with a clear 'Site ID' description). The tool description adds nothing beyond the schema's parameter definition, so 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?

The description uses a specific verb 'Generate' with resource 'growth plan' and adds process detail ('syncs GSC, runs analysis'), clearly distinguishing it from 'get_growth_plan' which retrieves an existing plan. It unambiguously states what the tool does.

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?

The description clearly implies the tool is used to create a new growth plan for a site, and the parenthetical hints at the workflow. However, it does not explicitly contrast with sibling tools like get_growth_plan or gsc_sync, nor does it state when not to use it. The context is clear but exclusions are missing.

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