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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description contributes the returned field list (type, product, amount, cost, date, withdrawal date, technician), which is genuinely useful given there is no output schema, but it says nothing about pagination, ordering, or empty-result behavior.

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?

Two sentences, no filler, with the resource and returned fields front-loaded and the endpoint template appended as a compact scoping cue. Every clause earns its place.

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 read-only list tool with full schema coverage and no output schema, the description does the important extra work of enumerating returned fields. The only shortfall is the absence of any note on pagination flow or result ordering, both of which an agent must piece together from the schema.

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 all four parameters are already documented, including the parent enum and the next_page pagination convention. The description's 'one animal, field or crop planting' phrasing only loosely maps the enum values and adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 names the resource (treatment records), enumerates the returned fields, and scopes it to a single animal, field, or crop planting. The listing verb is only implied by the tool name, but the REST endpoint template makes the operation unambiguous. It is clearly a distinct resource from siblings like farmbrite_list_activities or farmbrite_get_animal, though it never names them.

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?

There is no when-to-use or when-not-to-use guidance, and no routing to related siblings such as farmbrite_create_treatment (to add a record) or farmbrite_get_animal (for the parent entity itself). The agent must infer from the endpoint template that exactly one parent type plus id is required.

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