list_decoration_preset_releases

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

With no annotations, the description carries the full burden. It usefully discloses that the tool requires Kiln Pro and that the releases are signed, but it does not clarify read-only behavior, pagination, return shape, or what happens for non-Pro callers. The marketing copy also distracts from behavioral disclosure.

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 first sentence is front-loaded and useful. The following lines are promotional copy about Free versus Pro features and an upgrade URL, which do not help an agent select or invoke the tool and add substantial noise.

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?

The description is incomplete for a tool with no annotations, no output schema, and one undocumented parameter. It omits return-value expectations, filtering behavior, default handling, and practical distinctions from nearby listing tools.

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?

There are two parameters and only 50% schema description coverage. The description does not explain the preset_id filter or the include_retired option; only include_retired has a schema-level default note. It therefore fails to compensate for the undocumented parameter.

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: list signed decoration-preset releases. It also notes the practical purpose of obtaining the id needed to apply one. It does not explicitly distinguish this from sibling listing tools such as list_decoration_preset_versions or list_decoration_presets, but the signed-release scope is clear.

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 phrase 'and the id needed to apply one' implies this should be used before applying a decoration preset. The Pro requirement is stated, but there is no explicit guidance on when to use this versus related list methods, nor when not to use it.

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