Get Flow Externalized Configurations

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

No annotations are provided, so the description carries the full burden. The verb 'Get' implies a read-only operation, but the description does not explicitly state that the tool has no side effects, requires no special permissions, or that it returns data without modifying state. Minimal transparency.

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, well-formed sentence that clearly communicates the tool's action and result. No redundant words, and the key information is front-loaded. Every word 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?

Given the tool's simplicity (2 params, no output schema), the description is adequate but incomplete. It does not specify the structure of the returned configuration (e.g., list or object), the meaning of the version parameter, or the artifactId's role. Missing details that would help an agent fully understand the tool's usage.

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 0%, and the description does not explain the parameters artifactId or version beyond the general purpose. It mentions 'endpoints, credentials names' as examples of configuration content but does not clarify what artifactId identifies or how version (default 'active') affects results. The description adds little to parameter understanding.

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 clearly states the tool retrieves externalized configuration parameters of an integration flow, with examples (endpoints, credentials names). This distinguishes it from sibling tools like get_integration_flow (flow details) and update_flow_configuration (modification).

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 on when to use this tool versus alternatives. The description implies use when needing configuration parameters, but lacks prerequisites, exclusions, or comparisons with siblings like get_flow_resources or search_message_processing_logs.

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