manage_thumbnail_config

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

With no annotations, the description responsibly discloses the mutating effects of import and reset ('replaces', 'reverts') and what show returns ('effective config'). It hints at destructive behavior without promising reversibility or permissions, which is acceptable for a config utility.

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 compact sentence that leads with the four main verbs, immediately scopes the resource, and appends concise per-action semantics. Every phrase earns its place; there is no redundancy.

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 two parameters and no output schema, the description covers the essential behavior for each action. It does not elaborate on edge cases like error handling or whether import/reset require confirmation, but the core information an agent needs to call it correctly is present.

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?

Although the schema already describes 'path' as a file path, the description adds directional context ('destination' for export, 'source' for import) and clarifies the role of each action. This goes beyond the raw schema, adding practical value.

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 names a specific resource (thumbnail template config) and lists four precise verbs (show, export, import, reset), each with a one-line behavior. It clearly distinguishes itself from sibling tools like manage_config by scoping to thumbnail generation configuration.

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?

It explains the purpose of each action and when each is appropriate (e.g., 'export writes to a file path', 'import replaces from a file path'). It does not explicitly mention when to avoid this tool or name alternatives, but the action-driven guidance makes the usage context clear.

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