Get soil properties for a location

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

Discloses data source and resolution, but with no annotations, fails to mention response format, rate limits, auth requirements, or behavior for invalid coordinates. Adequate but not comprehensive.

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?

Single sentence packed with essential information: action, data fields, source, resolution, depth variability. No filler, front-loaded with verb.

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?

Without output schema or annotations, provides sufficient context on returned data (specific soil properties) and source. Missing response structure and error handling, but adequate for a straightforward lookup tool.

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 descriptions for latitude, longitude, and depths. Description adds 'multiple depths' and source context but no extra meaning beyond schema. Baseline score 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?

Clearly states the tool fetches soil properties (texture, pH, organic carbon, water-holding) from SoilGrids for a given coordinate at multiple depths. Distinct from sibling tools focused on weather and crop advice.

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?

Implies use for soil data queries, but no explicit guidance on when to choose this over siblings like get_growing_conditions. Lacks when-not or alternative recommendations.

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