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

With no annotations, the description carries the full behavioral burden and largely succeeds: it discloses metadata stripping, watermark disruption, camera-physics injection, and parameter-specific effects such as Lanczos resampling and sensor-grain noise. It stops short of noting side effects like whether the original file is modified, but the core behavior is clearly exposed.

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 summary line is front-loaded and informative, followed by a tight per-parameter list. For 8 parameters, the length is justified and every sentence adds value beyond the schema.

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?

The description covers required input, all optional parameters, defaults, and the return value effectively. It lacks explicit sibling routing and edge-case or failure notes, but the parameter detail is sufficient for correct invocation.

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%, and the description fully compensates. Every parameter gets a purpose, default, and often details absent from the schema, such as grain_intensity range (1.0-2.5), camera_profile enum values, and micro_resample's 0.3% Lanczos behavior.

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 opens with 'Full anti-AI pipeline' and immediately names concrete operations: strips C2PA/EXIF, disrupts lattices/watermarks, and adds camera physics. This clearly identifies the resource and action, and distinguishes it from narrower siblings like strip_metadata_only and inject_camera_profile.

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 does not explicitly state when to use this tool versus alternatives or when not to use it. The 'Full anti-AI pipeline' phrasing and sibling names imply it is the comprehensive option, but the guidance is inferred rather than stated.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains that images undergo anti-AI processing but does not state whether originals are modified when output_directory is omitted, whether files are overwritten, or what side effects occur. It also does not disclose format support or failure behavior.

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 compact, with a one-sentence purpose followed by a short parameter list and a returns note. It repeats default values already present in the schema, but overall it is well organized and easy to scan.

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?

As a batch mutation tool with no annotations, this description leaves important operational details uncovered: overwrite semantics, what happens if output_directory is null, whether directories are created, and how errors across multiple images are reported. The output schema exists but is not shown, and the 'Returns' line is too thin to fill this gap.

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?

Although schema description coverage is 0%, the description's Args section adds useful meaning for all four parameters: directory_path is the input source, output_directory is an optional save target, camera_profile is injected, and grain_intensity controls sensor noise. It does not fully specify expected formats or effects, but it meaningfully supplements the raw schema.

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 names a specific action ('Sanitizes all images in a target directory') and a distinct purpose ('anti-AI detection processing'). It is clear that this is a batch operation, which helps distinguish it from single-file siblings like anti_ai_sanitize, though it does not explicitly name those alternatives.

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 directory-based scope and processing intent imply the tool is for batch sanitization, and the parameters indicate optional output handling. However, there is no explicit guidance about when to choose this tool versus strip_metadata_only, inject_camera_profile, or single-file processing.

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

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.

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

With no annotations provided, the description must disclose behavioral implications itself. It states the operation modifies a JPEG by injecting EXIF and returns confirmation, but it does not clarify whether the original file is overwritten, whether output_path defaults to in-place modification, or what happens if the input is not a 'clean JPEG'.

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 concise, front-loads the core purpose in the first sentence, and organizes parameter details and return behavior clearly under Args and Returns. Every sentence earns its place without padding.

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?

The description is adequate for a simple three-parameter tool and covers parameters plus return type, but it leaves meaningful gaps in usage context and behavioral caveats. It does not mention when to use this tool relative to stripping/sanitizing siblings, nor does it explain output_path omission semantics, which is important for a mutation tool with no annotations.

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?

Although schema description coverage is 0%, the description compensates well by naming all three parameters, explaining image_path as 'Path to the JPEG image file', listing valid profile_name values, and marking output_path as optional. It adds practical meaning beyond the bare schema, though it could clarify the default behavior when output_path is null.

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 a specific action ('injects realistic camera EXIF') and a resource ('clean JPEG'), naming example camera brands. It is distinguishable from sibling tools like inspect_image_metadata or strip_metadata_only, though it does not explicitly contrast itself with them.

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 choose this tool over its siblings, such as anti_ai_sanitize or batch_sanitize_directory. It does not mention prerequisites, exclusions, or typical workflows like post-stripping metadata restoration.

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

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

No annotations are provided, so the description carries the burden. It implies a read-only operation ('Inspects') and describes the return as a 'Diagnostic audit', which is useful. However, it doesn't explicitly state that it makes no modifications, or mention any permissions or edge cases like missing files or unsupported formats. The added detail about the output partially compensates but doesn't fully disclose behavioral scope.

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 compact and well-structured, with a lead sentence stating the purpose, followed by Args and Returns sections. Every sentence earns its place; no redundant or filler content. The key information is 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?

The tool is simple (one parameter) and has an output schema (not shown) that likely details the return structure. The description covers the purpose and return basics, but lacks any mention of usage context, error handling, or comparison to sibling tools. For a security-related inspection tool, agents might need to know when to prefer this over sanitization, which is missing.

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 input schema only names the parameter 'image_path' with type string, offering no description. The tool description adds meaning by stating 'Absolute or relative path to the image file,' clarifying the expected format and scope. Since schema coverage is 0%, this compensation is essential and well-executed.

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 function: 'Inspects an image for AI detection risks, C2PA manifests, and EXIF footprints.' This is a specific verb and resource with enumerated focus areas, making it easy to understand what it does and to differentiate from sibling tools like strip_metadata_only or anti_ai_sanitize, which are modification 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios where inspection is preferred over sanitization, nor does it indicate when not to use it. The sibling tools exist for related tasks, but the description gives no routing hints.

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

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does disclose what is stripped and that pixels are not modified, which is useful. However, it does not clarify the re-encoding implications of the 'quality' parameter, the effect of omitting output_path, or the irreversibility of metadata removal, and 'without modifying pixels' vs. 'compression quality' creates a mild ambiguity.

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 compact and front-loaded with the core behavior, and the Args/Returns structure makes it easy to scan. It contains no filler, and the parameter explanations are appropriately sized. It mildly repeats schema field names, but not in a wasteful way.

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 3-parameter tool with an output schema, the description covers the essential invocation details: input path, optional output path, and quality semantics. The main gaps are behavioral edge cases—what happens when output_path is omitted, and whether the tool supports formats other than JPEG/WebP—but the core calling context is sufficiently complete.

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 must compensate, and it largely does. It explains image_path as the input file, output_path as the optional cleaned-output location, and quality as JPEG/WebP compression quality with a range and default. It adds usable meaning beyond the raw schema, though it could go slightly deeper on what happens when output_path is null.

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 ('strips') and names the resource clearly: all metadata, C2PA manifests, and EXIF tags. It also adds a crucial scoping guarantee—'without modifying pixels'—which distinguishes it from pixel-altering sanitization tools and inspection tools. An agent can tell what this tool does without needing to open the schema.

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 implies single-image metadata-only stripping through 'image_path' and 'output_path', but it does not explicitly state when to choose this tool over siblings like batch_sanitize_directory or anti_ai_sanitize. There is no when-not-to-use guidance or named alternative, so the usage context is only implied.

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