Get all funnels

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

No annotations provided, and the description only restates the HTTP method and resource name. It does not disclose any behavioral traits such as pagination, rate limits, or response format, leaving the agent without additional guidance.

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 extremely concise, communicating the key purpose and API endpoint in just three short sentences. However, the inclusion of 'Tags: Funnels' may be extraneous for an agent.

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?

Despite the tool's simplicity, the description fails to mention what the response includes (e.g., an array of funnel objects or their key fields). Without an output schema, this omission leaves the agent without complete contextual understanding of the output.

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 the schema coverage is complete. The description does not need to add parameter semantics, so score 4 as per baseline.

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 action (GET) and resource (all funnels), and distinguishes from the sibling 'weeek_get_a_funnel' which retrieves a single funnel.

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 explicit guidance on when to use this tool versus alternatives, but the name and sibling 'weeek_get_a_funnel' imply its use for retrieving all funnels.

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