createPond

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states 'Create a pond' and does not mention side effects, permissions, idempotency, return values, or any other meaningful behavior beyond the obvious fact that it creates a resource.

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 very short, but it is under-specified and restates the tool name, so it does not earn its place. It is not verbose, but the content is so minimal that it fails to provide useful structure or information beyond the name.

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 mutating tool with no annotations and no output schema, the description should provide more context about what happens when a pond is created or what the resulting state is. 'Create a pond' alone is insufficient for complete understanding of 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 input schema already fully describes the only parameter 'name' with 100% coverage, so the description does not need to add parameter meaning. It earns the baseline score of 3, as it neither adds nor detracts from the schema's clarity.

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 'Create a pond' is essentially a plain-language restatement of the tool name 'createPond', providing no additional detail beyond the action and resource. It is not vague, but it qualifies as a tautology since it simply restates what the name already conveys.

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?

There is no guidance on when to use this tool vs. alternatives like listPonds, getPond, or updatePond. No prerequisites, exclusions, or contextual hints are provided, leaving the agent without direction on selecting this tool.

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