get_dataloggers

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well covered. The description's 'List' wording is consistent with those annotations but adds no additional behavioral context beyond what the annotations and purpose statement already convey.

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, efficient sentence that front-loads the core action and resource while adding a concise parenthetical definition of the datalogger types. Every word earns its place and there is no redundancy.

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?

This is a simple, one-parameter read-only tool with a rich annotation set and an output schema present. The description plus ready parameter guidance is sufficient for an agent to invoke it correctly; nothing critical is missing.

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%, and the plant_id parameter already has a clear description ('Plant ID, as returned by get_plants'). The tool description adds little beyond confirming the dataloggers are plant-scoped, so it does not substantially improve on the schema's parameter documentation.

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 uses a specific verb ('List') and resource ('dataloggers ... attached to a plant'), and explicitly clarifies what those dataloggers are (ShineWiFi / ShineLAN sticks). This makes the tool's scope clear and distinguishes it from broader sibling tools like get_devices or write-oriented tools like add_datalogger.

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 implies the tool is for retrieving dataloggers tied to a plant, and the schema reinforces that plant_id is required and sourced from get_plants. However, it does not explicitly name alternatives or state when not to use this tool versus, for example, get_devices or get_plant_details.

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