nasa_earth_imagery

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

The description does not disclose any behavioral traits beyond the bare action. It does not mention that the tool is read-only, requires an API key (though schema has api_key param), has rate limits, or what the output format is. With no annotations, the description carries full burden but fails to provide useful context.

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 sentence, which is concise but under-specified. It does not earn its place as it provides no useful information beyond the tool name. A longer, more informative description is needed for a tool with 5 parameters.

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 has 5 parameters, required lat/lon, and no output schema, the description is highly incomplete. It does not explain what the tool returns (e.g., image URL, file), date format requirements, or how to obtain an API key. This is insufficient for an agent to use correctly.

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 no meaning to any of the 5 parameters (lat, lon, date, dim, api_key). Schema description coverage is 0%, and the description does not explain what each parameter does, expected formats, or the role of the API key.

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 'Get' and resource 'NASA Earth satellite imagery', but it does not differentiate from sibling tools like nasa_mars_photos or nasa_epic. The name implies Earth imagery but the description lacks specificity.

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 on when to use this tool vs alternatives. The description does not mention prerequisites (e.g., API key) or context for use. Sibling tools exist for other imagery types, but no differentiation is provided.

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