get_sample

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose a genuine trait — that output text is bounded — and names the returned evidence types, but says nothing about permissions, how the change/output limits interact with offsets, or what happens on missing IDs.

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 front-loaded sentence with no filler. Its brevity is appropriate, though the trailing clause ("captures and exact weight-change evidence") is loose enough to read ambiguously.

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?

An output schema exists, so return values need not be described, but for a six-parameter tool with two pagination pairs and zero annotation or schema coverage, the description is far too thin. It should explain the run/case scoping and how the limit/offset pairs paginate.

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% across six parameters, so the schema provides no meaning for run_id, case_id, change_limit, change_offset, output_limit, or output_offset. The description alludes to bounded output but never maps the limits or offsets to parameters or explains their semantics, leaving half the interface undocumented.

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 and resource ("Read one sample") and enumerates the payload it returns (bounded output text, captures, weight-change evidence). The singular "one sample" implicitly separates it from the sibling get_samples, though the phrasing is compressed and grammatically awkward.

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 single-sample framing implies when to use it versus the plural get_samples, but no explicit when/when-not condition or alternative routing is stated. Usage must be inferred from the verb and the sibling name.

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