rb209_soil_methodology

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

With no annotations, the description carries the behavioral disclosure burden. It does communicate that this is a GET (read-only) operation returning an 'Individual' methodology, which is useful. However, it does not mention possible error conditions, authentication needs, output shape, or how the selected methodology relates to other soil data, leaving notable gaps.

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 sentence that immediately surfaces the HTTP method and endpoint path. The filtering clause is slightly redundant with the schema, but the overall structure is efficient and front-loaded with the most identifying information.

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 simple two-parameter GET endpoint, the description is minimally viable and the schema covers all parameters. However, there is no output schema, no mention of return format, and no context about where methodology IDs come from or what distinguishes this from rb209_soil_methodologies. Given the low complexity, a score of 3 reflects that it is adequate but not fully complete.

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?

Schema coverage is 100%, with both nutrientId and methodologyId described as filter ids. The description largely repeats this information ('filtered by nutrient id and methodology id') without adding extra meaning such as value sources, valid ranges, or relationships. Baseline 3 is appropriate because the schema already documents the parameters adequately.

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 clear verb-resource pair: 'GET /api/Soil/Methodology/{nutrientId}/{methodologyId}' and identifies it as an 'Individual soil methodology' endpoint. It also signals filtering by two IDs. However, it does not explicitly distinguish itself from the sibling rb209_soil_methodologies tool or define what a methodology is, so it stops short of full sibling differentiation.

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 about when to use this tool instead of alternatives such as rb209_soil_methodologies. The description merely restates the endpoint and filtering behavior, leaving the agent to infer usage context from the name and path. No exclusions, prerequisites, or alternative routing are provided.

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