save_screenshot_permanently

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

With no annotations provided, the description carries full behavioral burden, but it discloses no side effects, permissions, or downstream consequences. 'Permanently' implies persistence but does not clarify whether the session screenshot is moved, copied, or deleted, nor does it mention overwrite 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, grammatically complete sentence with no redundant words. It front-loads the core action and resource, earning high marks for conciseness and structure.

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 simple one-parameter tool with no output schema, the description gives the minimum viable statement of purpose, but it omits behavioral context such as what constitutes 'permanent', whether the operation is reversible, or what the tool returns on success. Given the lack of annotations, this is insufficient for an AI agent to use the tool confidently.

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 fully describes the single parameter 'index' with 100% coverage, so the description need not add more. The description itself adds no additional semantic meaning beyond the schema, hence the baseline score of 3.

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 'save' with a clear resource ('a screenshot from current session') and the adverb 'permanently' distinguishes it from temporary session screenshots. This clearly separates it from sibling tools like take_screenshot and list_permanent_screenshots.

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 does not mention that take_screenshot creates session screenshots or that list/read_permanent_screenshots handle retrieval, leaving the agent to infer the intended workflow.

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