get_catalog_policy_usage

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 the privilege requirement (superuser-only) and an API version constraint (Langflow 1.12.x), which is real added value. It does not state that this is a read-only aggregate, nor how large the catalog must be or whether results are paginated.

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 sentence that front-loads the operation and appends the two qualifying constraints. No filler, no restatement of the name.

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 zero-parameter aggregate tool with no output schema, the description should at least sketch the return shape (per-component flow counts). It covers the prerequisite and version scope but leaves the agent without any expectation of what comes 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 baseline is 4. The description adds nothing that could mislead about inputs, and there is no parameter surface to document.

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 and resource: counting flows that use each catalog component. It is clearly a distinct operation from the sibling list_components or create_store_component. However, it never distinguishes itself from the very similarly named sibling get_catalog_policy_usage_flows, leaving the agent to guess which of the two to call.

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 'superuser-only' conveys an important prerequisite for using this tool, which is genuine usage guidance. But there is no statement of when this is the right choice versus get_catalog_policy_usage_flows or the other policy tools, so routing between near-identical siblings is left to inference.

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