gugik_skorowidze

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

No annotations provided, so description must cover behavior. It describes a read-only lookup with no side effects, but lacks details on error handling, authentication, or performance. Adequate but not enriched beyond obvious.

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?

Single focused paragraph with clear purpose, dataset list, and usage context. No unnecessary words; front-loaded with key information.

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?

Covers essential aspects for a query tool: input parameters, output expectation (sheet and download link), and why you'd use it. With an output schema (indicated as present), the description is sufficiently complete for agent usage.

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 0%, so description compensates well by listing dataset options and explaining their meaning (same tile-index mechanism). Also mentions buffer_deg default. Adds value beyond 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?

Clearly states the tool looks up map-sheet index coverage at a point, providing sheet identifier and download link. Distinguishes from sibling download tools by noting it's the same mechanism but for non-download queries.

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?

Explicitly says it's for cases where you just want to know availability without downloading, implying alternatives (download tools) for actual downloads. Also lists valid dataset values.

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