get_model_provider_policy

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful behavioral context: it is read-only, requires superuser privileges, and is scoped to the Langflow 1.12.x API. It stops short of saying anything about the returned policy payload or its freshness, which matters since no output schema exists.

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 no filler: verb, scope, access requirement, and API version all land before the reader stops reading.

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 parameterless read tool with no annotations and no output schema, the definition covers identity and access prerequisites but leaves the return value entirely unexplained. An agent knows it can call the tool and who may call it, but not what it will get back.

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?

The tool takes zero parameters, so the schema provides nothing an agent could misread; the baseline of 4 applies. There is no parameter detail the description could add.

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 (Read) and resource (install-wide approved model-provider policy), distinguishing it from the write counterpart replace_model_provider_policy by implication. However, it never explicitly names that sibling, and the surrounding policy getters (get_policy_bundle, get_catalog_component_policy, get_catalog_template_policy) are not differentiated.

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?

No when-to-use guidance or alternatives are given. The reader cannot tell from the description when to call this rather than get_policy_bundle or get_catalog_component_policy, both of which return related policy data. The 'superuser-only' note is a prerequisite, not routing guidance.

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