get_camera_profiles

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

No annotations are present, so the description carries the full behavioral disclosure burden. 'Returns' does signal a non-mutating retrieval operation, which is useful, but the description does not disclose any potential failure modes, permissions, data source behavior, or whether profiles come from hardware, configuration, or storage. For a simple zero-parameter getter this is adequate but minimal.

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 with no filler or repetition. It front-loads the core action and object, and every word contributes to the meaning. It is as concise as possible while still being informative.

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 parameterless tool with an output schema available, the description only needs to convey what the tool returnschers. 'Returns available camera profiles and their specifications' is sufficient for an agent to invoke it correctly. There are no missing input requirements, edge cases, or configuration details that the agent would need for this particular call.

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 and the input schema is empty, so there is no parameter ambiguity for the description to resolve. The schema coverage is effectively complete, and the description adds a meaningful hint that the returned data includes camera profiles and their specifications. This meets the baseline for a parameterless tool.

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 uses a specific verb ('Returns') and a clear resource ('available camera profiles and their specifications'). It distinguishes the tool from siblings like inject_camera_profile and strip_metadata_only by establishing this as a read-only listing of camera profile data. The purpose is immediately obvious with no ambiguity.

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 usage guidance is provided. The description does not state when to use this tool versus alternatives, mention any prerequisites, or clarify when it should not be used. There is no explicit or even implied selection context beyond the basic function statement.

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