list_cameras

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

The description clearly implies it is a read-only listing operation with no side effects. No annotations are provided, but the description adequately covers behavioral transparency for this simple tool.

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 composed of two concise sentences: first stating the purpose and return data, second providing usage guidance. No redundant information, perfectly front-loaded.

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 no parameters and no output schema, the description is complete. It covers purpose, return content, and integration with other tools. No missing context for effective use.

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 tool has zero parameters, so the description carries no additional parameter burden. Baseline score of 4 is appropriate as no parameter documentation is needed.

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 tool lists camera presets for survey mission planning and specifies the exact data returned (sensor dimensions, focal length, FOV). It distinguishes itself from sibling tools by its role in mission planning and direct linkage to specific mission generation tools.

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 explicitly tells when to use this tool (for survey mission planning) and how to use the results (passing preset IDs as camera_model parameter to generate_grid_survey and generate_corridor_mission). This is excellent guidance for the AI agent.

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