adobe_config

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered structurally. The description adds that settings persist on the local machine, but omits what a write does to keys not mentioned (merge vs replace), whether the API key is echoed back, and what a read returns — meaningful gaps for a config mutation tool.

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 well-formed sentence with the action front-loaded and the key list following. Every clause earns its place, though the inline parenthetical glosses make it read as a slight list dump.

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?

No output schema exists, so the description should say what a read returns, and it does not; nor does it explain write/merge semantics or unknown-key handling. Annotations cover the safety side, but for a configuration tool the agent is left guessing about the read path and the effect on unspecified keys.

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% and the only parameter is an untyped-bag 'set' object, so the description must carry the semantics. It does enumerate the valid keys (pixabayKey, mediaDir, ytdlpArgs) and gloss their meaning, which is real compensation, but it never states that omitting 'set' performs the read, nor what value format each key expects.

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 pair (read/set) and a specific resource (Adobe Studio MCP settings stored on this computer), then enumerates the exact keys managed, so the agent knows precisely what the tool touches. It does not differentiate itself from nearby config-adjacent siblings such as adobe_setup, which keeps it short of a 5.

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 read-or-set framing implies when you'd call it, but there is no explicit guidance on preferring this over adobe_setup or adobe_status, and no statement of prerequisites or when not to use it. Usage is inferable rather than stated.

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