process_raw

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

With no annotations, the description carries full burden. It discloses that the tool returns an inline thumbnail when include_preview is True and mentions the profile controls parameters. However, it does not discuss side effects (e.g., file overwriting), authentication needs, or the main return value when thumbnail not requested.

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 relatively concise with 4 sentences, starting with the main action and then elaborating. The param list is included but could be more structured (e.g., bullet points). Still, it is not verbose and front-loads key information.

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 8 parameters and no output schema, the description is incomplete. It does not explain the return value when include_preview is False, nor does it specify constraints on output_format or quality settings. Missing details on profile requirements or output behavior leave gaps for an AI agent.

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 0%, so the description should compensate. It lists all 8 parameter names but only adds meaning for 'include_preview' (returns thumbnail). No explanations for allowed values, defaults, or constraints on other parameters like output_format, jpeg_quality, or bit_depth. The bare list is insufficient.

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's purpose: processing RAW files with a PP3 profile to convert to JPEG, TIFF, or PNG. It specifies the verb ('process'/'convert'), resource, and method. This distinguishes it from siblings like 'preview_raw' or 'batch_analyze' which serve different purposes.

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 a clear usage context: 'Use this to convert a RAW file to JPEG, TIFF, or PNG using a PP3 profile.' It implies when to use but does not explicitly exclude alternatives or mention when not to use. This meets the 'clear context, no exclusions' level.

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