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

With no annotations, the description must carry the behavioral load; it usefully discloses the auth requirement ('Requires a bearer key') and that a site id is returned. It does not cover whether creation is idempotent, what happens on a duplicate label/address, or any rate limits.

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?

A single tight sentence that front-loads the action, scopes the resource, and appends the return value and auth requirement with zero filler. Every clause earns its place.

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?

No output schema and no annotations mean the description should do more for a 5-parameter mutation tool: all parameters are optional yet the description never says whether a bare create is valid, nor what happens on conflicting duplicates. It does at least flag the returned site id and the bearer key, which an agent needs to chain into add_readings.

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 coverage is 60% (label, water_type, disinfectant documented; address and volume_gallons undocumented), and the description adds no parameter meaning at all. Nothing compensates for the two bare parameters, and the description's mention of 'pool, hot tub or splash pad' merely echoes the water_type enum values already in the schema.

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?

States a specific verb ('Open') and a specific resource ('a water-test log for one pool, hot tub or splash pad'), plus the return value ('returns a site id'). It is clearly the creation step among read/write siblings (add_readings, check_readings, get_log_summary), though it never names a sibling to sharpen the contrast.

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 'open a log first, returns a site id' framing implies this is the entry point before add_readings/check_readings, but that sequencing is left to inference. There is no explicit when-to-use, when-not-to-use, or named alternative.

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