listPonds

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read-only 'List' operation, but discloses nothing about pagination, sorting, response size, or side effects. While the read-only nature is implicit, the lack of any additional context or safety guarantees leaves significant behavioral ambiguity.

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 'List all ponds' that is front-loaded and devoid of filler. Every word carries meaning. It is appropriately concise for a zero-parameter list operation, achieving high clarity with minimal text.

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 low complexity (0 params, no output schema), the description is minimally viable but lacks context about what a 'pond' is and what the response contains. Without an output schema, the agent must infer the return structure. The description covers the basic intent but not enough for fully informed invocation and result handling.

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 zero parameters, so the input schema is complete and the description cannot add parameter-level detail. The baseline score of 4 applies as there is nothing to document or compensate for. No parameter information is needed.

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 'List all ponds' clearly states a specific action (List) and resource (ponds). It distinguishes itself from sibling tools such as getPond (single resource) and createPond/updatePond (mutations), and from list tools for other resources like listPeople and listNotes. The verb and noun are 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 explicit guidance on when to use this tool versus alternatives. There is no mention of use cases, exclusions, or comparisons to getPond or other list operations. The usage is only implied by the name and composition, which is insufficient for guiding an agent on selection.

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