rb209_advice_note_arable_scot

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

With no annotations provided, the description carries the behavioral burden. The explicit 'GET' signals a read-only operation, and 'full list' indicates the endpoint returns the complete set without filtering or pagination. It does not describe the response item shape, but for a parameterless list-retrieval tool, the core behavior is transparent.

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 a single well-front-loaded sentence: endpoint first, then result scope. It contains no filler, no repeated schema information, and every word contributes to understanding what the tool does.

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 parameterless list endpoint, the description is largely complete: it identifies the endpoint, the geographic/crop scope, and that the full list is returned. Since there is no output schema, a little more detail about whether the returned items are note identifiers, titles, or full text would be helpful, but the sibling set provides reasonable surrounding context.

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?

The input schema has zero properties and 100% schema description coverage, so there are no parameters for the description to explain. The zero-parameter baseline of 4 applies here; the description need not add parameter-level detail.

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 states a specific verb and resource ('GET /api/AdviceNote/ArableScot') and explicitly scopes the result to 'Scotland arable.' This distinguishes it clearly from sibling tools like rb209_advice_note_arable_eng_wal and rb209_advice_note_grass_scot. 'The full list of available advice notes' also makes the output general shape clear.

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 'Scotland arable' scope gives a clear contextual signal for when this tool is appropriate, and the sibling names make obvious alternatives such as the England/Wales arable and grass Scotland advice notes. However, the description does not explicitly name alternatives or state when not to use this tool, so it falls just short of full guidance.

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