create_pond

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. "Create a pond" implies a mutating write operation, but it does not describe permissions, side effects, response behavior, or idempotency. This is a significant gap for a create tool with no annotation support.

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 and front-loaded: "Create a pond. (POST /ponds)". It contains no filler or wasted words. The endpoint is somewhat redundant with the tool name and schema but harmless; the brevity is appropriate given the schema carries most detail.

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 tool with five parameters, nested objects, no output schema, and no annotations, this description is too thin. It does not explain what a pond is in this domain, the role of userId as lead agent, or what a successful creation returns. An agent cannot fully assess correctness from the description alone.

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?

Schema description coverage is 100%, so the input schema already documents all parameters including name, userId, userIds, extraBody, and extraQuery. The description adds no parameter meaning beyond the schema, which meets the baseline for fully covered schemas.

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?

Description states a specific verb and resource: "Create a pond" with the endpoint. This clearly differentiates from siblings like get_pond, list_ponds, and update_pond based on the create action. An agent can tell what the tool does without opening the schema.

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 gives no guidance on when to use create_pond versus alternatives. It does not mention that create_pond is for new ponds while update_pond handles existing ones, nor does it note prerequisites or conditions. Usage must be inferred entirely from the tool name.

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