rb209_advice_note_grass_scot

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

With no annotations, the description carries the full burden. It discloses a read-only GET operation and that the result is a full list, which covers the basics. However, it does not mention response format, ordering, or any access considerations, though the simple zero-parameter nature limits the gap.

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, focused sentence that states the endpoint and the result. It is front-loaded and contains no filler or redundant content.

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 zero-parameter list retrieval tool, the description provides the essential context: resource path, geographic/crop scope, and result type. It does not explain return item structure, but this is a simple list where 'advice notes' is reasonably self-descriptive.

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 tool has zero parameters, so the schema fully defines the input surface. The description appropriately focuses on what the tool returns rather than parameter details; the baseline for 0 parameters 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 clearly states a specific resource and action: it returns the full list of available advice notes for Scotland grass. The scope (Scotland grass) distinguishes it from siblings like rb209_advice_note_grass_eng_wal and rb209_advice_note_arable_scot.

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 intended use is clear from the explicit scope: use this tool when you need advice notes for grass in Scotland. It does not explicitly state when not to use alternatives, but the naming and description make the context unambiguous.

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