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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description does not contradict them. It adds useful scope (theme 'of this account') and impact (styling and media), but it does not state that applying the theme may replace existing catalogue styling or explain how expected_revision guards against that.

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 no filler. Every word contributes to identifying the operation and its scope.

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?

This is a destructive write with no output schema, no parameter descriptions, and no explanation of expected_revision. For an agent to invoke this safely, the description should at least indicate what value expected_revision takes and how to obtain it, so the current description leaves a meaningful gap.

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 must compensate. It refers to 'theme' and 'catalogue' in prose, but it never explains expected_revision—a required 64-hex field—or how it relates to the catalogue's current state.

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 and resource: 'Copies the styling and media of a theme of this account onto this catalogue.' This clearly identifies the operation and distinguishes it from theme creation/update tools like foliade_create_theme and foliade_update_theme.

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 implies the correct use case—applying an existing account theme to a catalogue—but it gives no explicit when/when-not guidance and does not name alternatives among the sibling tools. It is clear context without exclusions.

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