get_flow_responses

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

The annotations already provide readOnlyHint=true, indicating a safe read operation. The description adds the fact that results are paginated, which is behavioral context beyond annotations. However, it does not disclose other behavioral traits such as ordering, error handling, or limits.

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 concise sentence that front-loads the verb and resource. Every word contributes meaning with no fluff. It is appropriately sized for the tool's complexity.

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?

The description is minimal and does not cover the output structure or any additional context about the responses. Given no output schema, the agent lacks information about what fields are returned. For a paginated data retrieval tool, this omission is significant.

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 schema coverage is 0%, so the description must compensate. It mentions 'paginado', which hints at the use of page and per_page parameters, but does not explicitly describe any of the three parameters (flow_id, page, per_page). This provides some semantic value beyond the schema but is incomplete.

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 verb 'Obtiene' (gets) and the resource 'respuestas que los usuarios enviaron a través de un WhatsApp Flow', and includes 'paginado' indicating pagination. This distinguishes it from sibling tools like get_flow_assets and get_flow_screens, which retrieve different aspects of a flow.

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 implies usage for retrieving user responses from a WhatsApp Flow, but does not explicitly state when to use this tool versus alternatives, nor does it provide any when-not or context of prerequisites. The usage is implied by the tool name and context of siblings.

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