get_batch_readings

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

Annotations already mark readOnlyHint and idempotentHint, but the description adds crucial behavioral details: the series is downsampled evenly, first and last readings are always preserved, and the summary is computed over the full series even when downsampled. This goes well beyond the annotations.

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 well-organized with a brief purpose, a concise behavioral note, and clearly labeled Args and Returns sections. It is appropriately sized for the tool's complexity, with every sentence contributing meaningful information.

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?

The description covers downsampling semantics, parameter effects, and the full return summary fields. It is self-sufficient for an agent to correctly invoke the tool, even without an explicit output schema present.

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 0%, but the description's Args section fully explains each parameter: batch_id as the batch _id, latest_only as returning the most recent reading, and downsample_to with the meaning of 0 (disable downsampling). This compensates completely for the schema's lack of descriptions.

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 opens with 'Fetch fermentation readings (Tilt or manual) for a batch,' which uses a specific verb and resource, clearly distinguishing it from sibling tools like get_batch or list_recipes.

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?

While the description does not name alternative tools, it provides clear context for when to use this tool (active ferment with thousands of points) and explains the downsampling trade-off. It lacks explicit exclusions or when-not-to-use guidance.

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