set_screenshots

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds the key behavioral consequence that enabling causes every subsequent action to return a screenshot. It does not say whether the setting persists, the default state, or whether it can be toggled mid-session without side effects, but it adds real context beyond the annotations.

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?

A single front-loaded sentence with the effect in parentheses; every clause earns its place and there is no 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?

An output schema exists so return values needn't be explained, and the core mutation is clear. However, for a two-required-parameter mutation tool with undocumented parameters, the description leaves gaps around session_id format and the semantics of enabled that an agent must guess.

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 bears full responsibility. It only loosely maps 'for a session' to session_id and 'on or off' to the enabled boolean; it gives no format for session_id, no statement of what true/false mean, and no defaults.

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 ('Turn ... on or off') and resource ('per-step screenshots ... for a session'), and the parenthetical clarifies the effect, distinguishing it from the sibling 'screenshot' tool. It is clear but doesn't explicitly name the sibling it contrasts with.

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 effect '(each action then returns a screenshot)' implies when to enable, but there is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g., an open session), and no alternatives named.

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