landis_natmap_thematic_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 agent knows the operation is safe and repeatable. The description's 'Summarize' aligns with read-only behavior but adds no further disclosure about side effects, permissions, or rate limits.

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, front-loaded sentence that communicates the core operation and inputs with no wasted words. It is appropriately sized for a simple tool.

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 leaves ambiguity about whether bbox or geometry must be provided, since the schema only requires productId. It also does not mention that the two spatial inputs are alternatives or what happens if neither is supplied. With an output schema present, return values are covered, but the input semantics are incomplete for correct invocation.

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 only 25%, so the description must compensate. It does add meaning by identifying bbox and geometry as spatial selectors ('across a bbox or GeoJSON polygon') and by naming geometry as a GeoJSON polygon, but it does not explain the relationship between bbox and geometry or their format beyond the schema.

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 uses a specific verb ('Summarize') and resource ('one NATMAP thematic product') and specifies the spatial scope ('across a bbox or GeoJSON polygon'). It clearly states what the tool does, though it does not explicitly differentiate from sibling tools like landis_natmap_area_summary.

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 no guidance on when to use this tool versus alternatives such as landis_natmap_area_summary or landis_natmap_point. There is no mention of prerequisites or scenarios where this tool is preferred.

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