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

No annotations are provided, so the description carries full burden. It discloses the action (strips metadata) and the browser-based nature, which is useful privacy context. However, it does not mention whether the original file is modified, output format, or any limitations, leaving some ambiguity about 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 a single sentence with a useful parenthetical. Every word contributes to clarity, with no redundancy or filler.

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 browser-based tool, the description covers the core purpose and privacy context. It could mention output details or explicitly note that it is not for PDFs, but these are not essential for basic selection and 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?

The input schema has zero parameters, so there is nothing to document. The description doesn't add parameter semantics, but with 0 params the baseline is 4, and it provides no misleading or conflicting information.

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 the specific verb 'Strip' and clearly identifies the resource ('photos') and the data removed ('GPS location, camera info, and metadata'). This distinguishes it from sibling tools like pdf-metadata-remover, which targets PDFs instead of photos.

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 usage for photos that need EXIF removal and adds the context that it is a browser-based tool. It does not explicitly name alternatives or exclusions, but the scope is clear from the word 'photos'.

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