landsat_latest

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It fails to explain what 'most recent' means (acquisition date vs. processing date), which satellite platforms are included (e.g., Landsat 8/9), or what happens when no scene is found. The output format is also unspecified.

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 a single concise sentence that front-loads the core purpose. However, it is slightly too brief given the tool's complexity and lack of annotations, missing some important context that would not be wasteful to include.

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 the 3 parameters, the absence of output schema, and many sibling tools, the description is insufficient. It does not specify the return format (e.g., a scene ID or metadata), temporal interpretation of 'most recent', or any limitations like scene availability. An agent would lack key information 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 coverage is 100%, so the baseline is 3. The description does not add any meaning beyond the schema's parameter descriptions (lat, lng, max_cloud). For example, it does not explain how max_cloud filters scenes or that the tool returns the scene with the lowest cloud cover within the limit.

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 verb 'Find' and the resource 'most recent Landsat scene for a location', which precisely identifies the tool's function. It distinguishes itself from sibling tools like landsat_search (general search) and landsat_timeline (temporal patterns) by focusing on the single most recent scene.

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 when you need the latest scene, but it does not explicitly state when not to use it or mention alternatives. There is no guidance on using landsat_search for more specific queries or landsat_timeline for temporal trends, leaving the agent to infer context.

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