mars_rover_status

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

With no annotations, the description carries the full burden. It usefully discloses two caveats — the weather feed only runs for Curiosity and `show_photos` is a no-op after the Photos API retirement — but it does not say what 'status' actually contains, whether data is live or cached, or how errors surface. The headline promise of 'latest photos' also sits awkwardly against the later admission that no photos are fetched.

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?

Two-sentence headline followed by a compact Args block; every line adds information an agent needs, and the return scope is front-loaded before the parameter notes.

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?

For a 2-parameter read with no output schema and no annotations, the description covers both parameters, the resource scope, and the two behavioral caveats. What's missing is a sense of the response shape for 'status' (e.g. sol, instrument state) — modest, but noticeable with no output schema to lean on.

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 there are no enums, so the description does real work: it names the two valid `rover` values including the default, and explains that `show_photos` is retained only for compatibility and returns nothing. Minor gap: it doesn't say what happens if an unknown rover name is passed.

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 first sentence names a specific resource (NASA Mars rover) and the three things returned: current status, weather, and latest photos. It is clearly distinguishable from siblings like planetary_rover_location_map, but it never explicitly contrasts itself with them.

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 Args block gives effective selection guidance for `rover` (weather only works on MSL/Curiosity), which implies 'pick curiosity if you want weather'. However, there is no statement of when to use this tool versus adjacent siblings such as planetary_rover_location_map or iss_now, and no explicit exclusions.

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