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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value beyond that: it states the return ordering (page order), discloses what is excluded (images and layout settings), and notes the API key/access requirement. It stops short of describing pagination or error behavior.

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 first two sentences restate the same fact ('text elements ... with an ID per element' and 'returns the text elements ... each with an element ID'), which is redundant. It is front-loaded and reasonably short, but one of those sentences does no work.

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 read-only getter with no output schema, the description conveys what comes back (text elements in page order with element IDs) and what does not (images, layout). Combined with the annotations covering the safety profile, an agent has enough to invoke it correctly; only pagination/scale details are absent.

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 100% (step_id is documented as 'Funnel step ID from list_funnel_steps'), so the schema carries the parameter burden. The description adds nothing about step_id syntax or format beyond repeating the element-ID concept, so the baseline 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?

Specific verb+resource: returns the text elements (headlines, paragraphs, buttons) of one funnel page, each with an element ID. It distinguishes itself from the relevant sibling update_page_text by describing the workflow handoff, and from list_funnel_steps via the step_id reference, so an agent can identify it without opening another schema.

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?

It gives clear context for use: fetch element IDs, then pass them to update_page_text. The auth prerequisite ('Needs the user's Cotlet API key with access to this app') is also stated. However, it does not explicitly state when NOT to use it or name alternatives beyond the downstream update tool.

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