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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: it discloses the required auth ('Cotlet API key with access to this app') and that results come back in funnel order, which the annotations do not imply.

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?

Information-dense and front-loaded with the resource and its fields. The opening fragment ('Your sales funnels with their steps: name, type, URL path and page ID') and the following sentence overlap slightly on the same idea, but every sentence still carries usable 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 carries the burden of describing returns and does so by naming the step fields and their ordering. Combined with the auth requirement and the full-coverage parameter schema, an agent has everything needed to call it correctly.

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?

There is a single parameter and schema description coverage is 100%, with the schema already stating 'Only this funnel. Default: all funnels.' The description's 'Leave funnel_id out to list every funnel' restates that default without adding format or ID-syntax detail, so the baseline of 3 applies.

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 specific verb and resource (lists funnels with their steps) and enumerates the returned step fields (name, type, URL path, page ID), so the agent knows exactly what this returns. It also distinguishes itself from the page-manipulation siblings by explaining that each step's ID is what the page tools consume as step_id.

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 explicit parameter-level guidance: 'Leave funnel_id out to list every funnel,' which tells the agent when to scope vs. not scope. It also explains the downstream purpose (step IDs feed the page tools), giving clear usage context, though it names no alternative listing tool to prefer instead.

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