landis_soilscapes_area_summary

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that the tool accepts bbox or GeoJSON geometry, but does not disclose additional behavioral traits such as output structure, pagination, coordinate system expectations, or behavior when both bbox and geometry are provided. It provides marginal value beyond the annotations but not rich context.

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, concise sentence that front-loads the main action and resource. It contains no fluff and is immediately understandable. Every word earns its place.

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?

Given that an output schema exists, the description doesn't need to explain return values. It covers the primary input options and the purpose. The schema note clarifies the anyOf constraint (bbox or geometry), and the description's 'or' aligns with that. It doesn't mention potential limitations or edge cases, but for a straightforward summary tool with read-only annotations, it is largely 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 description coverage is 0%, so the description is the only source of parameter meaning. It mentions 'bbox' and 'GeoJSON Polygon/MultiPolygon', which map to the bbox and geometry parameters, and implies they are alternatives via 'or'. However, it does not specify the exact bbox format (e.g., [minLon, minLat, maxLon, maxLat]) or coordinate system, leaving room for ambiguity. It partially compensates for the schema gap but not fully.

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 verb 'Summarize' and the specific resource 'LandIS Soilscapes coverage', and specifies the accepted input geometries (bbox or GeoJSON Polygon/MultiPolygon). This is sufficiently specific to distinguish it from sibling tools like landis_natmap_area_summary, which targets a different dataset, and landis_soilscapes_point, which is point-based.

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 description gives no explicit guidance on when to use this tool versus alternatives. While the name and resource mention Soilscapes, it doesn't state when an agent should choose this over other area-summary tools (e.g., landis_natmap_area_summary, ons_geo_area_summary) or mention exclusions or alternatives. The usage context is only implied by the resource name.

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