fetch_wdl_from_dockstore

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does ('下载工作流' - download workflow) without mentioning any behavioral traits such as whether it requires authentication, has rate limits, what happens if the download fails, or what the output looks like. For a tool with zero annotation coverage, this is a significant 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 description is extremely concise with a single sentence '从Dockstore下载工作流' (download workflow from Dockstore). It's front-loaded and wastes no words, though this conciseness comes at the cost of completeness. Every word earns its place in conveying the core purpose.

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 that there are no annotations, schema description coverage is 0%, and the tool has a parameter (config with url and output_path), the description is incomplete. While an output schema exists (which reduces the need to describe return values), the description doesn't address behavioral aspects, parameter meanings, or usage context. For a download operation that likely involves network calls and file system operations, more context is needed.

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 description provides no information about parameters. With schema description coverage at 0% (the schema has descriptions but they're minimal and generic), the description doesn't compensate by explaining what 'config' contains, what format the 'url' should be, or what 'output_path' means. For a tool with 1 required parameter (a nested object with 2 properties), this leaves significant gaps in 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 states the tool's purpose as '从Dockstore下载工作流' (download workflow from Dockstore), which provides a clear verb ('下载' - download) and resource ('工作流' - workflow). However, it doesn't differentiate from sibling tools like 'search_dockstore' or 'import_workflow', leaving ambiguity about when to use each. The purpose is clear but lacks sibling differentiation.

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 description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'search_dockstore', 'import_workflow', and 'validate_wdl', there's no indication of whether this tool is for initial downloading, validation, or import processes. No explicit or implied usage context is provided.

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