get_batch

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

Annotations already declare read-only/idempotent/non-destructive behavior. The description adds valuable context about large payloads and the ability to trim via sections, as well as the return structure including dual units.

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 efficiently structured with a purpose statement, Args/Returns sections, and no wasted words. It front-loads the key information and includes necessary detail.

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?

Despite lacking an explicit alternative mention, the description is complete for a read-only fetch tool: it explains purpose, parameters, return content, and payload-size implications, with annotations covering safety.

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 0%, but the description fully documents both parameters: batch_id as 'from list_batches' and sections with a complete list of valid values and the default behavior of returning everything when omitted.

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 'Fetch one batch in full, or just the sections you need,' using a specific verb and resource, and distinguishes from sibling tools by emphasizing full vs partial retrieval and payload trimming.

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?

Implied usage is clear: use this to retrieve a specific batch with optional section filtering. However, it does not explicitly mention alternatives like get_batch_readings for measurements or list_batches for finding IDs, so it lacks explicit when-not or alternative guidance.

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