rb209_previous_cropping_previous_grasses

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

With no annotations, the description carries the behavioral disclosure burden. The 'GET' prefix and 'full list' language indicate a read-only lookup with no side effects, but it does not mention auth requirements, rate limits, or response shape. For a simple zero-parameter lookup this is adequate but not rich.

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, compact line that front-loads the HTTP endpoint and immediately states what is returned. Every word contributes to understanding, with no filler or repetition.

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 endpoint, the description supplies the essential information: the full URL path and the semantic meaning of the result. It is sufficient to invoke correctly, though it does not describe the output structure or differentiate itself from the singular sibling.

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 and an empty input schema, so parameter documentation is unnecessary. The baseline of 4 for no-parameter tools applies here; the description correctly adds no redundant parameter details.

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 the HTTP method and resource ('GET /api/PreviousCropping/PreviousGrasses') and defines the tool as returning 'The full list of available previous grasses.' The plural 'grasses' and 'full list' signal that this is the list variant, though it does not explicitly contrast with the singular sibling tool rb209_previous_cropping_previous_grass.

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 phrase 'full list' implies use when a complete enumeration of previous grasses is needed, but there is no explicit guidance on when to choose this over the singular sibling or other list endpoints. It gives an implied usage context rather than clear selection criteria.

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