get_flow_node_catalogue

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile needs no repeating. The description still adds real value beyond them by disclosing that the payload is partly account-scoped (custom fields, tags, services, existing flows, comment triggers, plan caps), which tells the agent the result varies per account and can be used to plan around limits. It says nothing about response size or shape, which is the main remaining gap.

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 content is front-loaded and information-dense, but the last two sentences restate material already given: "Read this before writing a flow definition" duplicates "Read it before composing a definition," and "It lists every node type, its config fields and output ports" repeats the list in sentence two. Roughly a third of the description is redundant, which costs it on this dimension.

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?

With no input parameters and no output schema, the description carries the full burden of telling the agent what comes back, and it does so thoroughly by inventorying trigger sources, node types, ports, enums, placeholders, rules, and account-specific options. What it omits is any sense of payload shape or size, which matters for a catalogue payload this broad, so it falls just short of 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 tool takes no parameters, so there is no per-argument meaning to add; baseline 4 applies. The description correctly describes a zero-argument call, leaving nothing ambiguous about invocation.

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?

Names a specific verb and resource ("Get the node catalogue") and then enumerates exactly what the catalogue contains: trigger sources with channels and keyword requirements, node types with input/output ports and config fields, enums, placeholders, structural rules, plus live account data. That enumeration makes it unmistakable versus siblings like get_flow_definition or get_flow, which return actual flows rather than the build-time vocabulary.

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 directive is explicit and repeated: read it before composing a flow definition. That is clear when-to-use guidance. It stops short of naming alternatives (validate_flow, create_flow) or an explicit when-not-to-use case, so it lands at 4 rather than 5.

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