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

No annotations are provided, so the description carries the burden. It does disclose that the source is unverified and requires isolated ingestion, which is valuable. However, it does not state whether the operation is read-only or any permission requirements, leaving some ambiguity for a download tool.

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 two sentences, front-loaded with the core action and output, and includes the important caveat about verification. No redundant information or fluff.

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?

The description covers the output (base64, SHA-256, rights) and the caveat, but it omits any explanation of the study_id parameter and does not mention limitations such as file size or authentication. Given the simple scope, it is partially complete but lacks essential parameter semantics.

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 purpose or format of the required study_id parameter. Since there is only one parameter, this is a significant gap; an agent would not know what value to supply without additional context.

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 action 'Download' and the resource 'starter ZIP', specifying it returns base64, SHA-256, and rights. It also distinguishes itself from siblings like get_starter_study (metadata) by focusing on the actual ZIP download.

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?

There is no explicit guidance on when to use this tool versus the siblings (e.g., get_resource, get_starter_study). The description implies its purpose but does not state exclusions or conditions for alternative choices.

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