nasa_epic_date

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

With no annotations provided, the description carries full burden. It discloses that EPIC captures 12-22 images per day and returns image URLs, captions, and centroid coordinates. This adds behavioral context beyond the basic purpose, though it omits potential error conditions or rate limits.

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 highly concise: two sentences with no wasted words. The first sentence states the core action, and the second adds valuable context about image count and return fields. Front-loaded and efficient.

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 tool's simplicity (single parameter, no output schema), the description adequately covers what the tool does and what it returns. It does not discuss error handling or edge cases, but for a straightforward date-based retrieval, this is sufficient.

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% for the single 'date' parameter. The tool description reinforces the parameter's role ('specific date') but does not add new semantics beyond what the schema's description already provides. Baseline 3 is appropriate.

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 function: 'Get DSCOVR EPIC full-Earth photographs for a specific date.' It specifies the resource (DSCOVR EPIC photographs) and distinguishes itself from siblings like nasa_epic_latest (likely latest image) and nasa_epic_archive.

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 a specific date but provides no explicit guidance on when to use this versus alternatives like nasa_epic_latest or nasa_epic_archive. No exclusions or when-not-to-use scenarios are mentioned.

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