list_funnels

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

The description adds that stages are included in the listing, but otherwise the readOnlyHint annotation already covers the safety profile. No additional behavioral traits (e.g., pagination, ordering) are disclosed, so the description provides marginal added value beyond annotations.

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 single sentence that front-loads the verb and resource. Every word serves a purpose, with no extraneous 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?

Given the tool has no parameters and no output schema, the description adequately covers the core function. However, it could add details about ordering, pagination, or the exact structure of the stages, but these are not critical for a simple list operation.

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?

The tool has no parameters, and schema description coverage is 100%. The description does not need to explain parameters, and it correctly conveys that the tool lists funnels with stages, which is consistent with the schema's empty properties.

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 clearly states the tool lists all sales funnels with their stages, using a specific verb ('lista') and resource ('embudos'). It distinguishes itself from sibling list tools by specifying 'de la cuenta Wasapi' and 'con sus etapas', making the purpose 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 provides no guidance on when to use this tool versus alternatives like list_campaigns or list_labels. An agent must rely solely on the tool name, which may not be sufficient given many list tools exist.

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