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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: the tool returns a URL rather than inline data, the payload is GeoJSON, and parts can be several megabytes. It omits whether the URL is temporary/signed, whether authentication is required to fetch it, or any rate limits, leaving meaningful gaps.

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?

Two short sentences, front-loaded with what is returned and followed by the operational instruction. No filler; every sentence carries information, though the second sentence could note the id's origin for equal efficiency.

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?

Since there is no output schema, the description correctly explains the return value (URL + description, GeoJSON, size). For a 2-param tool with no annotations it still leaves the `id` parameter and URL validity/auth details unaddressed, so it is adequate but not fully self-sufficient.

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 coverage is only 50%: `part` is documented ('two-letter state, or "all"'), but `id` has no description anywhere. The description adds nothing about what `id` refers to or where it comes from, so it fails to compensate for the coverage gap.

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 states a specific resource (one part of a dataset) and return shape (GeoJSON URL plus its description), which tells an agent what the tool produces. It does not explicitly contrast itself with siblings like get_layer or get_source, but the resource is unambiguous enough to distinguish them in practice.

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?

"Fetch the URL for the features" implies the follow-up workflow, which is useful usage context. However, there is no guidance on when to use this versus list_datasets, get_layer, or get_source, and no stated prerequisites (e.g., needing an id from list_datasets).

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