get_aoi_soil_summary

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

No annotations are provided, so the description bears the full burden. It discloses the tool's read-like behavior via 'Returns' and enumerates the exact fields, and it adds the key qualifier 'no ratings.' However, it omits any mention of side effects, permissions, rate limits, or edge-case behavior, offering only moderate transparency.

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 concise, with two sentences covering purpose, output fields, and usage context. It is front-loaded with the primary action and contains no filler, making every sentence valuable.

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?

The description successfully conveys the tool's purpose, outputs, and use cases, and an output schema exists to document return values. However, it lacks parameter-level details and explicit guidance on when to prefer this tool over siblings, leaving notable gaps in completeness.

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%, and the description does not explain 'wkt' or 'landunit.' While the parameter names are somewhat self-explanatory, the description fails to specify formats, coordinate systems, or how landunit is used, leaving a significant gap in compensating for the missing schema descriptions.

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 explicitly states the tool returns map units and major components intersecting an AOI, and conspicuously notes 'no ratings,' distinguishing it from sibling rating tools. It also lists specific output fields, removing ambiguity about the tool's scope.

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 provides clear context by naming two use cases (transparency E4, leaching/water-table screening W4). It also implies a non-rating exclusion with 'no ratings,' but it does not explicitly reference alternative tools or provide comprehensive when-not-to-use conditions.

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