get_mars_rover_photos

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('가져옵니다' - fetches) but doesn't describe what the tool returns (e.g., list of photos, metadata, pagination), error conditions, rate limits, or authentication needs. For a tool with 4 parameters and no output schema, this leaves critical behavioral aspects undocumented.

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, concise sentence in Korean that directly states the tool's function. It's front-loaded with the core action and resource, with no wasted words. However, it could be more structured by including key usage hints, but as-is, it's efficiently written.

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's complexity (4 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return format (e.g., what 'photos' entail), pagination behavior implied by the 'page' parameter, or how parameters interact (e.g., sol vs. page for date filtering). Without annotations or output schema, the description should provide more context to compensate, which it fails to do.

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 100%, with clear descriptions for all parameters (camera, page, rover, sol), including enums for rover and camera. The description adds no additional parameter semantics beyond what the schema provides, such as explaining relationships between parameters (e.g., sol vs. page). Since the schema is comprehensive, the baseline score of 3 is appropriate.

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 '화성 로버의 사진을 가져옵니다' (Fetches photos of Mars rovers) states the basic action and resource but is vague about scope. It doesn't specify whether it retrieves all rover photos, recent ones, or filtered results, nor does it distinguish this tool from sibling tools like 'search_nasa_images' which might also return Mars rover photos. The purpose is understandable but 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'search_nasa_images' or explain if this is for specific rover missions, filtered queries, or general browsing. Without context, users must infer usage from parameters alone, which is insufficient for effective tool selection.

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