get_mars_rover_manifest

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

No annotations are provided, so the description carries the full burden. It describes the data returned (mission details) but lacks behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, or error handling. The description does not contradict annotations, but it fails to disclose key operational aspects beyond the basic function.

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 appropriately sized and front-loaded, starting with the core purpose followed by details and parameter explanation. Every sentence adds value, though the structure could be slightly more streamlined by integrating the parameter details more seamlessly.

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 low complexity (1 parameter, no output schema, no annotations), the description covers the basic purpose and parameter semantics adequately. However, it lacks details on behavioral aspects (e.g., read-only nature, error cases) and does not fully compensate for the absence of annotations and output schema, leaving gaps in operational context.

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?

With 0% schema description coverage and 1 parameter, the description compensates by explaining the parameter's purpose ('Name of the rover') and providing valid values (curiosity, opportunity, spirit). This adds meaningful context beyond the bare schema, though it could specify format constraints (e.g., lowercase).

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 specific action ('Get the mission manifest') and resource ('Mars rover'), listing the exact rovers (Curiosity, Opportunity, Spirit) and detailing the mission information provided (landing/launch dates, status, etc.). This distinguishes it from sibling tools like get_mars_rover_photos, which focuses on photos rather than manifest data.

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 by specifying the rover names and the type of data returned, but it does not explicitly state when to use this tool versus alternatives (e.g., get_mars_rover_photos for photos instead of manifest details). No exclusions or prerequisites are mentioned, leaving some ambiguity for the agent.

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