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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the underlying REST path, but nothing about behavior on an unknown id (empty vs error) or auth requirements — acceptable given the annotation coverage, but not enriching.

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 short fragments, front-loaded with the resource and scope, no filler. Slightly clipped to the point of being telegraphic, but nothing is wasted.

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-parameter read tool with full annotations, this is close to sufficient: the agent knows it fetches one plot by id. With no output schema, though, the description gives no hint of what a returned plot contains or how a missing id is signaled, which is the main remaining gap.

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?

Only one parameter and schema description coverage is 100%, with the schema itself explaining that plot_id is a Farmbrite id string with a pattern and length bounds. The description adds no format or sourcing detail beyond what the schema supplies, so the 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?

Identifies the resource ('field/grow location') and the single-item scope ('by id'), with the endpoint GET /plots/{plot_id} confirming it's a read of one plot. It stops short of naming the obvious sibling farmbrite_list_plots, so the distinction is implied rather than stated.

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?

'By id' implies this is the single-record fetch versus the list tool, and the presence of farmbrite_list_plots in the sibling set makes the split inferable. However, there is no explicit when-to-use/when-not statement and no guidance on what to do if only a name is known.

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