get_decoration_preset

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

With no annotations provided, the description does carry the burden, but it does disclose an important non-schema detail: the operation requires Kiln Pro and includes an upgrade link. 'Fetch' implies a read operation, which is low risk, but the description does not explain invalid-ID behavior, whether one of the two IDs must be supplied, or what 'full record' contains.

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 core sentence is front-loaded and useful, and 'Requires Kiln Pro' earns its place. But the sentence about Kiln Pro saving this as a reusable feature or decoration preset is promotional and irrelevant to invoking this tool, and the upgrade URL adds clutter rather than invocation guidance.

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?

There is no output schema and no annotations, and both parameters are undocumented at schema level. The description should therefore clarify required-ID behavior and return expectations, but it only says 'full record,' leaving the agent without enough information to reliably select the correct ID combination or understand the response.

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 for preset_id and preset_version_id. It only hints at the distinction through 'single preset or an exact version,' but does not say which parameter is required, whether both may be supplied, or how the two selection modes interact.

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 first sentence gives a specific verb and resource: 'Fetch ONE decoration preset — the full record for a single preset or an exact version.' It scopes the operation to a single record, which helps distinguish it from list operations in spirit, but it never names the sibling alternative such as list_decoration_presets, so sibling differentiation is only implicit.

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?

Usage is implied by 'Fetch ONE' and 'full record,' suggesting this is for retrieving a single preset rather than listing presets or versions. However, there is no explicit when-to-use guidance, no stated alternative, and no conditions distinguishing preset_id lookup from preset_version_id lookup.

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