load_geodata

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

Annotations already indicate readOnlyHint and destructiveHint. The description adds that the tool caches data into DuckDB and describes the force_refresh parameter, providing behavioral context beyond annotations.

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: one clear sentence plus two brief argument descriptions. No unnecessary words, and the structure is effective.

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?

Given an output schema exists, the description adequately covers purpose and parameters. It might miss details about prerequisites (e.g., DuckDB spatial extension), but overall is sufficient for a loading tool.

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?

With 0% schema documentation coverage, the description fully compensates by explaining both parameters: resource_id (prefixed or bare ID) and force_refresh (re-download even if cached), providing essential meaning.

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 clearly states the tool's action: downloading and caching a geospatial resource into DuckDB with spatial support. It specifies supported formats (SHP, KML, GeoJSON), making the purpose specific and distinguishable from siblings that may not target DuckDB or spatial data.

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 implies usage for geospatial data loading to DuckDB but does not explicitly contrast with siblings like 'download_resource' or 'cache_manage'. No when-to-use or alternatives guidance is provided.

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