get_epic_imagery

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation but doesn't disclose critical traits like whether it returns latest images, requires authentication, has rate limits, or provides metadata. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 extremely concise and well-structured, with a clear purpose statement followed by parameter details in a labeled 'Args' section. Every sentence earns its place, and there is no redundant or verbose content.

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 lack of annotations and output schema, the description is incomplete for a tool that likely returns complex imagery data. It doesn't explain what the tool returns (e.g., image URLs, metadata, date ranges), how results are formatted, or any limitations, leaving the agent with insufficient context for effective use.

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?

The description adds meaningful context for the single parameter 'collection' by listing options ('natural', 'enhanced'), which compensates for the 0% schema description coverage. This clarifies the parameter's purpose beyond the schema's basic type and default, though it doesn't explain what these options entail or their differences.

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 images') and resource ('from the EPIC (Earth Polychromatic Imaging Camera)'), making the purpose immediately understandable. It distinguishes from siblings like 'get_earth_imagery' by specifying the EPIC camera source. However, it doesn't explicitly contrast with 'get_epic_imagery_by_date', leaving some ambiguity about scope.

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_epic_imagery_by_date' for date-specific queries or 'get_earth_imagery' for broader Earth imagery, nor does it specify prerequisites or contexts for usage.

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