clawhub_download

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

With no annotations, the description must disclose all behavioral traits. It mentions the response includes base64-encoded zip bytes and size, but omits critical details: whether the operation is destructive, authentication requirements, error handling (e.g., missing slug), and rate limits. Insufficient for safe agentic use.

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?

Two concise sentences deliver key information without redundancy. Every word serves a purpose, making it easy to parse.

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?

For a simple download tool with three parameters and no output schema, the description covers the core purpose, required/optional parameters, and response format. It lacks error scenarios or further contextual cues, but is largely sufficient given low complexity.

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 coverage is 0%, so description adds essential meaning. It specifies that 'slug' is required, and 'version' and 'tag' are optional with 'defaults to latest.' This clarifies default behavior not captured in schema. However, it does not define the semantics of 'version' vs 'tag' or any constraints.

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 'Download a skill as a zip archive,' specifying a concrete action and resource. It distinguishes from siblings by focusing on the full skill download rather than search or individual file retrieval, though it does not explicitly differentiate from tools like clawhub_get_file.

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?

Provides parameter guidance (required slug, optional version or tag with default) but gives no indication of when to use this tool versus alternatives like clawhub_get_skill or clawhub_get_file. Missing when-not-to-use or comparative context.

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