ga4_top_conversion_paths

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

No annotations are provided, so the description carries the burden of explaining behavior. It does disclose the output composition, sort order, and the 'convenience report' nature, which implies a read-only analytics operation. However, it does not explicitly state read-only behavior, date handling, property fallback, or any limits/pagination, leaving some behavioral gaps.

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?

Two sentences with no filler. The core report behavior is front-loaded, and the client-context sentence earns its place by clarifying the intended use. It is appropriately sized for the tool's simplicity.

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 output schema covers return values, so the description need not explain those. The description conveys the report's purpose and composition, but it leaves parameter semantics and usage boundaries unaddressed. For a four-parameter tool with no annotations, this is still a noticeable completeness gap.

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%, and the description does not explain any of the four parameters (limit, start_date, end_date, property_id). The parameter names and defaults are somewhat self-explanatory, but the description adds no meaning beyond the schema and does not compensate for the absence of parameter descriptions.

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 exactly what the report returns: sessions by source/medium, conversions, conversion rate, sorted by conversions descending. It also frames the business question it answers. It does not explicitly name a sibling alternative like ga4_run_report, so it stops short of full differentiation, but the purpose is unambiguous.

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 implies when to use it: when the client needs to know which channels produce leads. However, it provides no explicit guidance on when NOT to use it or which alternative tool should be used for custom or more detailed reports. Usage context is present but not exclusionary.

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