get_flow_elements_catalog

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only labels the content as a catalog and does not describe whether the operation is read-only, what response format to expect, or any other behavioral traits beyond the name's implication.

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 description is a single short sentence with no filler or repetition. It is appropriately sized for a zero-parameter catalog retrieval, though it could have added slightly more practical detail without becoming verbose.

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 catalog tool, the description gives a minimally viable idea of what the tool returns. However, with no output schema and no behavioral or usage details, an agent is left to infer the return format and whether any side effects or prerequisites exist. The low complexity makes this acceptable but not fully 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?

The input schema has zero parameters, so there are no parameter semantics for the description to clarify. Per the baseline for 0-parameter tools, this is fully adequate; nothing is missing on this dimension.

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 identifies the resource ('elementos de flujo') and clarifies scope by naming what is included: flows and gateways. This distinguishes it from sibling catalog tools like get_activities_catalog or get_markers_catalog, even though the verb is implied rather than stated.

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 explicit guidance is given about when to use this tool versus the many sibling catalog tools. The parenthetical '(flows, gateways)' provides an implicit context cue, but the description never states a selection rule or mentions alternatives.

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