Set screenshot headline/caption (local draft)

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

With no annotations, the description must disclose behavioral traits. It indicates a write operation ('Set') but omits side effects, permissions, synchronous/asynchronous behavior, and whether it overwrites existing text. This is insufficient for agents to understand impact.

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?

Two sentences: first states the action, second provides critical guidance. No unnecessary words, information is front-loaded. Every sentence earns its place.

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 5 parameters, no output schema, no annotations, and multiple sibling tools, the description is too sparse. It does not explain the relationship between base-language and translations, what happens on success, or how variantId is used. Agents would likely need to infer or fail without additional context.

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 40% (only appId and slotIndex have descriptions). The description adds character limits for headline and caption, which partially compensates. However, variantId is not explained, and textType enum values are only implied. The description adds some value but not enough for low coverage.

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 action: 'Set the base-language headline or caption for a screenshot slot.' It uses specific verbs and nouns, and the title reinforces 'local draft'. This distinguishes it from siblings like update_screenshot_translation and get_screenshot_texts.

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 character limit guidance but does not indicate when to use this tool versus alternatives such as update_screenshot_translation for translations or get_screenshot_texts for reading. No explicit when/to-when-not advice is given.

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