getPond

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

With no annotations, the description carries the burden of behavioral disclosure. The verb 'get' clearly indicates a read-only operation, but no other behavioral traits are mentioned, such as return format or error behavior on missing IDs. For a simple getter, this is minimal but not severely deficient.

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, front-loaded sentence with zero filler. It efficiently conveys the exact operation and key qualifier, making it perfectly concise for a tool of this simplicity.

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 tool is very simple (one required parameter, no output schema), and the description covers the core operation. However, it leaves out any mention of what is returned (the pond object) or how failures are handled. This is a minor gap, but complete enough for an agent to infer typical get-by-ID 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 input schema fully covers the single parameter 'id' with the description 'Pond ID' (100% coverage). The description's 'by ID' simply echoes the schema, adding no extra semantic context or constraints beyond what the schema already provides.

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 'Get a pond by ID' clearly states the action (get) and resource (pond) with the key identifier (ID). It distinguishes itself from sibling tools like listPonds (which lists many) and createPond/updatePond (which mutate), leaving no ambiguity about its scope.

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?

No explicit guidance is given on when to use this tool versus alternatives. The existence of listPonds implies a distinction, but the description does not articulate it. Usage is implied rather than directly stated.

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