funnels_get_pages_by_funnel_id

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds the fact that it returns a list, which is minor. It does not disclose pagination behavior or that the result is paginated, which would be useful, but given the annotations, a 3 is appropriate.

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 concise single sentence that front-loads the primary action. It avoids unnecessary words and is easily readable. However, it is so brief that it borders on under-specification, hence a 4 rather than a 5.

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 tool with five parameters and only 20% schema coverage, the description is incomplete. It does not mention that funnelId is the identifier, that results are paginated via limit/offset, or any details about the returned list. Without an output schema, the agent lacks critical context to call the tool 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?

Schema description coverage is only 20% (only locationId has a description). The description provides no parameter explanations, leaving the purpose of funnelId, limit, offset, and name unexplained. With low coverage, the description should compensate, but it does not, so a score of 2 is warranted.

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 'Fetch list of funnel pages' clearly states the action (fetch list) and resource (funnel pages). It distinguishes from related tools like 'funnels_get_funnels' (which gets funnels) and 'funnels_get_pages_count_by_funnel_id' (which gets a count). However, it is terse and could explicitly mention that it is filtered by funnel ID, though the name already implies this.

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 offers no guidance on when to use this tool versus alternatives, nor does it mention required parameters like funnelId or pagination (limit/offset). There is no explicit context for when an agent should choose this over other funnel-related tools.

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