nc_get_piezometers

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the action without describing return format, pagination behavior, data granularity, or any access or rate constraints. For a simple getter it is minimal but still lacks transparency about what the agent will actually receive.

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 with no superfluous words. It front-loads the core action and resource, making it easy to parse quickly.

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 there is no output schema, the description should at least indicate what the response contains (e.g., coordinates, site names, time series). It does not. The tool has only two optional parameters, so complexity is low, but the absence of any usage or result details leaves it incomplete for practical calling.

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 provides 100% coverage for both parameters ('Max results' and 'Filter by commune'), so the baseline is 3. The description adds no extra meaning beyond the schema; it does not clarify the format of 'commune' or how 'limit' interacts with paging.

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 clearly states the verb ('Get'), the resource ('piezometer locations'), and the purpose ('for groundwater level monitoring'). It is specific enough to distinguish from sibling tools like nc_get_rain_stations or nc_get_water_catchments, each of which targets a different monitoring type.

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 offers no guidance on when to use this tool versus alternatives, nor does it mention any conditions, prerequisites, or filtering strategies. An agent is left to infer that this is the only tool for piezometer data, but there is no explicit usage context.

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