landsat_search

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

No annotations provided, so the description must carry the full burden. It lacks details on output format, pagination, or error behavior. It only states filtering criteria without disclosing what happens with results (e.g., returns list of scenes, metadata, etc.).

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 sentence, no wasted words. Front-loads the core action and filtering dimensions. Efficient for an agent to parse.

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 no output schema and many sibling tools, the description is too brief. It does not explain what the search returns (e.g., scene IDs, metadata, browse URLs) or how to interpret results. Lacks completeness for an agent to reliably use without additional context.

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 has 100% description coverage for all 6 parameters. The description adds value by specifying the satellite family (Landsat 8/9) and unifying the filtering dimensions (location, date range, cloud cover) beyond individual param descriptions.

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 it searches Landsat 8/9 satellite scenes by location, date range, and cloud cover. The verb 'search' and specific satellite identifiers distinguish it from sibling tools like landsat_bands or landsat_metadata.

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?

No explicit when-to-use or alternative guidance. The description implies usage for scene search but does not differentiate from other landsat tools beyond the basic purpose. Agents must infer from tool names.

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