screenstudio_presets

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety baseline is covered. The description adds genuinely new behavioral context the annotations cannot: the interaction where an open editor retains stale settings and its next save writes them back over the preset, which warns against a specific destructive sequence.

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?

Front-loaded with the two modes, then a compact caution sentence. Dense but every clause earns its place; no filler or repetition.

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 dual-mode tool with no output schema, the description covers both actions and the destructive apply workflow adequately. It could say more about what 'list' returns, but the safety-relevant behavior is well covered.

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 0% for three parameters, so the description must carry the burden. It conveys the mapping implicitly (apply a preset to a project file => presetPath + projectPath, list needs none), but never explains the parameters by name, their formats, or which apply to which action.

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 two specific verbs (list/apply) against a specific resource (the person's saved Screen Studio presets), and clarifies that apply uses 'the app's own preset apply' rather than the editor's settings path. Clear without opening the schema, though it does not name the nearby sibling screenstudio_editor_apply explicitly.

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?

Gives a concrete when-to-use constraint: apply to a project that is NOT open in the editor, because an open editor will overwrite the preset on its next save. Strong contextual guidance, though no alternative tool is named for the editor-open case.

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