get_catalog_policy_usage_flows

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the auth requirement ('superuser-only') and version context ('Langflow 1.12.x API'), but says nothing about pagination behavior, return shape, or whether it is a pure read beyond the verb '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?

A single front-loaded sentence that states the action, the resource, and the access constraint with no 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 simple two-parameter read tool with a full schema and no output schema, the description covers purpose and auth adequately. However, it omits when-to-use guidance relative to its policy siblings, leaving a gap for an agent choosing among several catalog-policy tools.

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 both parameters (limit and component) are already documented in the schema. The description adds the concept that 'component' is the catalog component key being blocked, but no syntax or format detail beyond the schema, so 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 gives a specific verb (List) and a well-defined resource (flows affected by blocking a catalog component key), which is far more informative than the name alone. It does not explicitly distinguish itself from the sibling get_catalog_policy_usage, but the 'affected flows' scope is clear enough for an agent to reason about.

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?

There is no guidance on when to use this versus the closely related get_catalog_policy_usage or the policy tools. No prerequisites, preconditions, or exclusions are stated, so the agent must infer the use case entirely.

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