replace_catalog_template_policy

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

With no annotations, the description carries the full burden. It adds the important behavioral detail that this is 'superuser-only' and version-gated ('1.12.x'), which is a useful constraint. But it doesn't disclose what 'replace' means for existing state (full overwrite), whether it's destructive, or any rate limits.

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 that conveys the action, target, and key constraint (superuser-only, version) without any wasted words.

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 a mutation tool with no annotations and no output schema, the description is minimal. It discloses the privilege requirement and version scope but omits the full-replacement semantics, potential side effects, and what the response might contain. It's adequate but with clear gaps for a destructive operation.

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 100%, so the schema already fully documents the single 'blocked' parameter. The description adds no additional parameter meaning beyond the 'global blocked-template' context, which is a baseline 3 per the rules.

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+resource ('Replace the global blocked-template catalog policy'), clearly identifying the operation. However, it doesn't differentiate itself from sibling tools like get_catalog_template_policy or replace_catalog_component_policy, which share the same 'catalog policy' domain.

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 parenthetical '(superuser-only Langflow 1.12.x API)' hints at a privileged context, implying when the tool might be used, but it provides no explicit guidance on when to use this vs. get_catalog_template_policy or other policy replacement siblings. Usage is only implied.

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