replace_catalog_component_policy

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

With no annotations supplied, the description carries the full burden, and it does add one real behavioral fact: the operation is superuser-gated. It does not state that the call is a full-overwrite operation (effectively destructive to any keys not resubmitted), nor whether it is idempotent or how failures are handled, so significant behavioral gaps remain for a privileged mutation.

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 the verb and resource first and the scoping constraints in parentheses. No filler, nothing that could be trimmed without losing information.

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 one-parameter mutation with no output schema or annotations, the description supplies the essentials: what is replaced, its global scope, and the privilege requirement. It would be fully complete if it noted that the supplied list replaces the entire policy rather than merging with the existing one.

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 is only one parameter and schema description coverage is 100%, with the schema already explaining it as the "Complete blocked component key set" — which is the key semantic (whole-set replacement, not append). The description adds nothing beyond that, so the baseline 3 applies.

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 pairs a specific verb ("Replace") with a specific resource ("global blocked-component catalog policy"), clearly setting it apart from the read-side sibling get_catalog_component_policy and from replace_catalog_template_policy. It stops short of explicitly naming those siblings, but the resource is unambiguous.

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 discloses the gating condition ("superuser-only") and the API scope (Langflow 1.12.x), which tells an agent who may call it. However, it offers no guidance on when to prefer this over replace_catalog_template_policy or replace_policy_bundle, leaving the agent to infer the distinction.

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