Download Integration Flow (base64 zip)

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

No annotations exist, so the description carries full burden. It only discloses the output format (base64 zip) but fails to mention non-destructive nature, authentication needs, rate limits, or response size. This is insufficient for understanding behavioral traits.

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 very short (one sentence), which is concise, but it sacrifices clarity and completeness. It lacks structure and does not efficiently convey needed details.

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 has 2 parameters with 0% schema coverage and no output schema or annotations, the description is woefully incomplete. It does not explain what the zip contains, how to use parameters, or any edge cases. Needs significant expansion.

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%, but the description adds no explanation for parameters like artifactId or version (default 'active'). Only 'zip ($value)' hints at output but not how parameters affect it. Minimal added value beyond schema.

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' and the resource 'integration flow content' as a base64-encoded zip. The term '($value)' is ambiguous but overall the purpose is clear and distinguishable from siblings like get_integration_flow.

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?

Only a brief hint 'Useful for backup/transport' is provided. No when-to-use or when-not-to-use guidance, and no mention of alternative tools like get_integration_flow or list_integration_flows.

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