earth.now

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

No annotations provided, so description carries full burden. It lists the kinds of data returned but doesn't detail behavior like how hours parameter affects results, rate limits, or authentication needs. Some transparency is present but incomplete.

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?

Single sentence, concise and front-loaded with purpose. However, it could include a brief note on parameter usage without significantly increasing length.

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?

With no output schema, the description should provide more structure on what's returned. It lists categories but not field names or nesting. For a composite tool, more completion information would be helpful.

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 0%, and the description adds no explanation for any of the 5 parameters. The agent must infer that lat/lon are coordinates, hours maybe for forecast period, radius_km for quake search radius, etc. This is insufficient.

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 it provides composite situational awareness for a coordinate, listing specific data types (timezone, local time, sunrise/sunset, nearby quakes, current weather). This is a specific verb+resource combination that distinguishes it from sibling tools like timezone.lookup or quakes.recent.

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 explicit guidance on when to use this tool vs alternatives. The description implies it's for a quick overview, but doesn't mention that individual tools might be better for specific needs or that this combines multiple APIs.

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