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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the specific funnel stages and rate calculations, which is useful. However, it does not clarify aggregation behavior, date handling, or how scope parameters affect results, and there is no output schema to compensate.

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 that communicates the core function, the funnel stages, and a primary use case without wasted words. Every element earns its place.

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 11 parameters, no output schema, and many closely related sibling tools, this description is too thin to fully orient an agent. It explains what the funnel contains but not how the parameters shape the result, what time range is used, or when a different PPC tool would be more appropriate.

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 description provides no parameter-level guidance. Schema coverage is 64%, meaning several parameters lack descriptions, and the description does not compensate for the gap. For example, it does not mention date range, ad type, or scoping semantics beyond the high-level funnel concept.

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: 'Get conversion funnel data' and clearly defines the resource as a funnel from Impressions to Clicks to Orders with conversion rates. This is more specific than the title alone, though it does not explicitly differentiate itself from sibling PPC analytics tools.

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 gives a usage context: 'Useful for health check analysis.' This implies when the tool is relevant, but it does not provide explicit guidance on when to choose this tool over alternatives such as ppc_daily_trend, ppc_period_comparison, or ppc_query.

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