nasa_epic_earth_imagery

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

No annotations are provided, so the description carries the full burden. It mentions 'Get' imagery but does not disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, rate limits, or what the return format looks like (e.g., image URLs, metadata). For a tool with no annotations, this is a significant gap in transparency.

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, efficient sentence that front-loads the core purpose ('Get full disc imagery of Earth') without unnecessary details. Every word earns its place, making it highly concise and well-structured.

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 annotations and no output schema, the description is incomplete. It does not explain what is returned (e.g., image data, links, metadata), error conditions, or other behavioral aspects needed for effective use. For a tool with 3 parameters and no structured output information, the description should provide more 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 description coverage is 100%, so the schema already documents all parameters (image_type, date, limit) with descriptions and defaults. The description does not add any meaning beyond what the schema provides, such as explaining the significance of 'natural' vs 'enhanced' imagery or date constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Get'), the resource ('full disc imagery of Earth'), and the source ('from DSCOVR's Earth Polychromatic Imaging Camera'). It specifically distinguishes this tool from sibling tools like 'nasa_apod' or 'nasa_mars_rover_photos' by focusing on Earth imagery from a specific satellite instrument.

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 Earth imagery, but does not explicitly state when to use this tool versus alternatives like 'nasa_apod' (astronomy) or 'nasa_mars_rover_photos' (Mars). It provides context (Earth imagery from EPIC) but lacks explicit guidance on exclusions or comparisons to sibling tools.

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