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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that – no mention of pagination via limit/cursor, default status filtering, or whether steps are included by default.

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?

One short sentence with no filler, but its brevity stems from under-specification rather than disciplined editing. Nothing is front-loaded because nothing substantive is stated.

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?

For a 7-parameter list tool with zero schema description coverage and no output schema, the description provides almost nothing an agent needs to call it correctly – no pagination behavior, no filter semantics, no return shape.

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% across 7 parameters, so the description must compensate and largely does not. The words 'steps' and 'checkout rails' faintly hint at include_steps and status/funnel_ref, but limit, cursor, workspace, funnel and the status enum are left entirely unexplained.

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 names resources (funnels, steps, checkout rails) but uses the ambiguous verb 'Read', so an agent cannot tell whether this lists funnels or retrieves a single one. It also fails to distinguish itself from siblings like funnels_analytics_get or checkout_get.

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?

There is no guidance on when to use this tool versus alternatives such as funnels_analytics_get, checkout_get, or pages_list. No prerequisites, no mention of when-not to use it.

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