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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so 'Read-only' is redundant, but the description adds genuinely new behavior: GeoJSON output format, default page of 500 and a hard ceiling of 5,000 features. It does not mention pagination past the cap or error behavior when a collection id is invalid.

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?

A single front-loaded sentence: the action and output format come first, then optional constraints, then collection id conventions. Every clause (bbox ordering, limit cap, id sourcing) carries information the agent needs.

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?

With no output schema, the description still names the return format (GeoJSON) and bounds the result volume. All three parameters are explained and the required collection id's provenance is resolved, leaving nothing essential unstated 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 0%, yet the description fully compensates: bbox axis order [west, south, east, north] is spelled out, limit's default (500) and maximum (5,000) are given, and collection is tied to find_layers ids. These are semantics the schema alone cannot convey.

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 ('Get a vector layer's features as GeoJSON from Biohotspot's OGC API'), which is clearly distinct from the sibling find_layers that only enumerates layers. The bbox and limit scoping further pins down what the call returns.

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?

It routes the agent to the correct prerequisite by naming find_layers as the source of collection ids, and says use exmouth_<dataset> for example project layers. There is no explicit when-not guidance or mention of alternatives like look_in_area, which keeps it from a 5.

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