websex_exiftool

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

With no annotations, the description carries the full burden. It usefully discloses that exiftool executes directly with supplied argv tokens and that shell parsing is never used, plus the engagement-namespace execution context. However it omits what the tool actually does to files (metadata read, not mutation), any permission/auth requirements, and resource limits.

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?

Three short sentences with no filler, and the core action is front-loaded. The execution-model detail follows naturally and every sentence adds 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?

An output schema exists, so return values need not be explained. The description covers the execution model, working-directory semantics, and engagement scoping; only stdin handling and any permission/side-effect notes are missing, which is a minor gap for a command wrapper.

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. It partially does: 'arguments' are argv tokens, 'working_directory' is implied by 'use relative paths', and engagement_id maps to the 'selected engagement namespace'. But 'stdin' is never explained, leaving a documented gap.

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?

States a specific verb and resource: run exiftool from the WebSex forensics toolkit. The tool's function (metadata extraction via exiftool) is clear from the resource name, though it does not explicitly contrast itself with sibling forensics tools like binwalk, strings, or xxd.

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 explicit when-to-use or when-not-to-use guidance, and no naming of alternatives among the many sibling forensics tools. The only usage hint is 'use relative paths for engagement artifacts', which is a constraint rather than selection guidance.

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