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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description's 'Read-only' adds little. It does add useful return-shape context ('with a few values from each') and narrows the domain to sea polygons, but it does not explain empty results, result size, or spatial edge cases.

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 front-loaded and efficient, with the core action stated immediately. 'Read-only' is redundant with annotations, and the description is so terse that it omits useful routing and output detail, but it contains no wasted prose.

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 one-parameter spatial listing tool with safety annotations, this is mostly enough to invoke correctly. However, with no output schema, the vague phrase 'a few values from each' leaves the return shape unclear, and the description does not address empty results or how this differs from closely related siblings.

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 100%, and the only parameter is documented as a GeoJSON Polygon in WGS84. The description adds that the polygon is on the sea, which is mildly useful, but it does not clarify coordinate constraints, land polygons, holes, or validity requirements 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?

States a specific verb and resource: list every Biohotspot map layer with data inside a sea polygon, including a sample of values. This is clear, but it does not distinguish the tool from siblings such as look_here, understand_area, find_layers, or get_features.

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 spatial context ('inside a polygon on the sea') implies when the tool is appropriate. However, it gives no explicit when-to-use or when-not-to-use guidance, and it does not route the agent among the many similarly named sibling tools.

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