Get record

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

The readOnlyHint annotation already establishes this is a safe read, so the description's remaining job is to add context. It does add one useful non-obvious detail — the response includes affected animals/groups — which is real value since no output schema exists, but it says nothing about farm scoping behavior or error cases.

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 the resource, the required identifier, and the payload scope. No filler or 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?

For a single-item read with readOnly annotations and full schema coverage, the definition is nearly sufficient, and it partially compensates for the missing output schema by naming what the record includes. It lacks any note on behaviour when farm_id is omitted or the record is not found.

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%, so both parameters (farm_id, record_id) are already documented in the schema; the description only restates record_id as a UUID. Baseline 3 applies when the schema carries parameter semantics.

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 ('Get a single record') and adds the key identifier ('by its UUID'), so it is clearly distinct from list_records/create_record/update_record. It does not explicitly name a sibling, so it stops short of a 5.

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?

Usage is only implied: 'by its UUID' tells the agent it needs a known record ID, which is enough to infer it should be used after a listing or creation step rather than for discovery. No explicit when/when-not or pointer to list_records for searching.

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