List Funnels

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

The description adds 'all' and 'for a location' which clarify scope but does not disclose pagination, ordering, or response format. Since annotations already declare readOnlyHint=true and destructiveHint=false, the safety profile is covered, but the description adds limited behavioral detail beyond the 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 concise sentence that front-loads the purpose and scope. Every word earns its place, with no redundant 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?

For a simple read-only list tool with strong annotations, the description provides the essential 'what' and 'for what'. It does not detail return structure, but given the low complexity and absence of an output schema, the coverage is adequate for an agent to infer the tool's behavior.

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 has one parameter (locationId) with no description and not marked as required. The description mentions 'for a location' but does not clarify whether locationId is mandatory, what format it should take, or what happens if omitted. With 0% schema description coverage, the description should compensate but does not sufficiently.

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 ('Get all') and the resource ('funnels/websites') for a specific scope ('for a location'). It effectively distinguishes the resource type from sibling list tools, though it does not explicitly differentiate usage from other list tools.

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?

Usage is implied: use this tool to retrieve all funnels/websites for a given location. However, there is no explicit guidance on when to prefer it over alternatives, what to do if no locationId is provided, or any exclusions.

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