replace_model_provider_policy

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

With no annotations, the description carries the full behavioral burden. It discloses that the operation is a replacement, is install-wide, and requires superuser privileges, which is useful context. But it does not warn that the previous policy is overwritten or that the approved_provider_ids list completely replaces the existing set, nor does it describe reversibility or error behavior.

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 description is a single, tight sentence with the action and scope front-loaded. Every element earns its place: the verb, the resource, the scope, and the auth/version constraint. There is no wasted wording.

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, the description covers the essential context: what is replaced, the installation-wide scope, the superuser requirement, and the Langflow version. It does not explain the effect on existing providers or the response format, but those gaps are minor given the simple schema and lack of an output schema.

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%, and the sole parameter is documented in the schema as 'Complete approved provider ID set.' The description adds no additional semantic detail about the parameter beyond what the schema already provides. With high schema coverage, the baseline score of 3 is appropriate.

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 states a specific verb and resource: 'Replace the install-wide approved model-provider policy.' It is clearly distinguishable from sibling get_model_provider_policy by the verb, and from replace_catalog_component_policy/replace_catalog_template_policy by the resource name. The scope is also specified as install-wide.

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 gives useful context ('superuser-only Langflow 1.12.x API'), which implies who can use it and the relevant version. However, it does not state when to choose this tool over alternatives such as get_model_provider_policy or the other policy-replacement tools, nor does it describe any exclusions or prerequisites beyond superuser access.

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