upload_translation_key_screenshot

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

The description says it replaces an existing screenshot, yet annotations declare destructiveHint: false, which is an annotation contradiction. Because of that contradiction, this dimension must be scored 1 despite the useful error-condition disclosure.

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 short, front-loaded with the core action, and uses bullets for parameter requirements and behaviors. It earns its place, though the replacement behavior is mentioned twice (description and base64 schema description), a minor redundancy.

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?

It covers required parameters, image format and size limit, replacement semantics, and failure when the key doesn't exist, which is enough for an agent to invoke the tool safely. With no output schema, it doesn't describe return values, but that's a minor gap for an upload operation.

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 coverage is 100%; both key and base64 have descriptions in the schema, and namespace is also documented. The tool description repeats these constraints (required, max 2MB, PNG/JPG/JPEG) rather than adding meaning beyond the schema, so baseline 3 applies.

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 states a specific action: upload a single base64-encoded screenshot for a translation key. It names the key resource and differentiates via 'base64-encoded' and singular 'a screenshot' from sibling file/bulk variants.

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?

It conveys when to use this tool (single base64 upload/replace) and its prerequisites, but it never explicitly contrasts it with upload_translation_key_screenshot_file or upload_translation_key_screenshots_bulk. The usage is implied rather than stated as when/when-not guidance.

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