get_cameras

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

With no annotations, the description must fully disclose behavioral traits, but it only states 'Get all configured cameras'. It does not mention read-only nature, idempotency, authentication requirements, or rate limits. The name implies reading, but behavioral specifics are lacking.

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 sentence that succinctly states the purpose. It is front-loaded with no extraneous words, achieving maximum conciseness for its informational load.

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 has no parameters and an output schema (which defines return structure), the description is nearly complete. It could optionally mention that it returns a list of cameras, but the output schema covers that. The description suffices for a simple retrieval tool.

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 there is no parameter information needed. According to guidelines, 0 parameters results in a baseline of 4, and the description does not need to add anything beyond the schema (which is empty).

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 verb 'Get' and the resource 'all configured cameras', distinguishing it from siblings like 'get_camera_snapshot' (gets a snapshot) and 'get_all_devices' (gets all device types).

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 guidance is provided on when to use this tool versus alternatives. For example, it does not mention that to get a snapshot, 'get_camera_snapshot' should be used, or that to get details of a specific camera, one might need another tool.

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