download_integration_flow

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

The description discloses that the tool downloads a ZIP file and returns base64-encoded content, which is useful. However, it does not mention error behavior, authorization requirements, or side effects. With no annotations, the burden is on the description, and it partially meets it.

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 concise sentence that efficiently conveys the core functionality and output format with no extraneous words.

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 existence of an output schema, the description adequately covers the return format. However, it fails to explain parameter semantics or provide usage context relative to siblings, making it minimally complete for a simple tool.

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 0% description coverage, and the tool description does not explain the parameters. 'iflow_id' and 'version' are not discussed beyond their names, leaving the agent without guidance on valid values or their roles.

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 verb 'Download', the resource 'integration flow', and the output format 'ZIP file (returns base64-encoded content)'. This distinguishes it from sibling tools like 'get_integration_flow' which likely return JSON.

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 guidance is provided on when to use this tool versus alternatives such as 'get_integration_flow' or 'get_iflow_resource'. The description lacks context for when to choose this download approach.

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