rb209_recommendation_calculate_nutrient_offtake

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the calculation operation and gives no detail on side effects, authorization needs, return behavior, or whether this is a pure read operation. It does not mislead, but it reveals very little beyond the action itself.

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 short line with no filler, and the endpoint is front-loaded. However, it is ungrammatical and compresses what could be a clear statement into a fragment, so the brevity comes at the cost of clarity.

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?

This is a nested-body POST with no output schema and no annotations, yet the description does not mention the response shape, required field semantics, or how this calculation relates to the many lookup sibling tools. An agent can construct the request from the schema but cannot predict the result or confidently know when this tool is the right choice.

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 schema covers all parameters with descriptions, so the baseline is 3 even though the description adds no parameter-level detail. The schema's generic 'The X Id for the crop' wording is sufficient for identifying the fields but does not explain how the IDs relate to each other or where to obtain them.

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 the endpoint and the operation: calculating the crop nutrient offtake value. This is specific enough to distinguish it from the sibling calculate_nutrient_deficiency tool, though the phrasing 'The calculate crop nutrient offtake value' is grammatically awkward.

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?

There is no guidance on when to use this tool versus alternatives such as rb209_recommendation_calculate_nutrient_deficiency or rb209_recommendation_recommendations. The intended selection context is left entirely to the agent to infer from the name and endpoint.

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