abx_get_all_flows_using_action

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. The description adds only the raw endpoint path and otherwise repeats the operation; it says nothing about pagination, result ordering, or the project-scoping behavior for non-system actions.

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 first two lines are near-verbatim restatements of each other and the third is a bare HTTP path, so roughly half the text is redundant. It is short and front-loaded, but the duplication means not every line earns its place.

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 read-only lookup with full schema coverage, rich annotations and no output schema, the definition is functionally adequate. It nonetheless omits the practical gotcha that non-system actions need a projectId, and gives no hint of the shape or size of the returned flow list.

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 are already documented, which sets the baseline at 3. The description corroborates that the ID identifies the action being searched for but adds nothing about the conditionally required projectId.

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: fetch/retrieve the list of action flows that use a given action, scoped by action ID. That is enough for an agent to distinguish it from the many abx_* CRUD siblings, though the description never explicitly contrasts itself with them.

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 when-to-use guidance, no mention of alternatives (e.g. abx_get_action_by_id for the action itself), and no note that non-system actions require projectId to be supplied. The agent must infer the usage context entirely.

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