list_model_provider_descriptors

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

No annotations are present, so the description carries the full behavioral burden. It discloses that results are limited to policy-visible providers and include stable IDs and display names, but omits permissions, pagination, and how the optional purpose parameter affects visibility. The read-only nature is only implied by 'List'.

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?

One sentence, front-loaded with the action and resource, with the version qualifier kept compact. There is no filler or repetition.

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 simple one-parameter list tool with no output schema or annotations, the description gives useful output-field context but leaves the optional 'purpose' semantics and sibling-tool choice unexplained. It is minimally adequate rather than complete.

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 single optional 'purpose' parameter already documents its enum values 'use' and 'configure'. The description adds no syntax, default, or behavioral meaning for that parameter beyond what the schema provides.

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 'List' and resource 'policy-visible model providers', plus output fields stable IDs and display names. It does not explicitly name sibling listing tools such as list_model_providers or list_enabled_providers, so differentiation is only implied by the 'policy-visible' qualifier.

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?

Offers an implied context via 'policy-visible' and the Langflow 1.12.x version, but never states when to choose this tool over list_model_providers, list_enabled_providers, or list_enabled_models. No exclusions, prerequisites, or alternatives are given.

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