rb209_arable_crop_info2s

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

No annotations are present, so the description carries the transparency burden. It communicates read-only behavior through 'GET' and 'full list', indicating no pagination or filtering. It does not disclose response format, ordering, or access prerequisites, but for a zero-parameter list endpoint the risk is low.

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?

One sentence with the endpoint front-loaded and the qualifier at the end; every phrase earns its place. No filler or redundancy.

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 covers the essential selection facts: what it returns and when it is required. The lack of an output schema is partially mitigated by 'full list'; more detail about the item structure would help, but isn't necessary to invoke the call.

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?

There are no parameters, so the empty schema fully specifies the call. With no inputs to document, the description does not need to add parameter semantics; the baseline of 4 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?

States a specific action: returns the full list of CropInfo2 records, with the scope 'only required for arable cereals crops'. The endpoint path in the description reinforces the resource. It does not explicitly contrast with sibling list endpoints like crop_info1s or the singular crop_info2, so not a 5.

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 'only required for arable cereals crops' gives a clear domain condition for when this lookup matters, implying it is not needed for non-cereal or grass scenarios. It does not name specific sibling alternatives, so it lacks explicit when-not/alternatives guidance.

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