Download repository package

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context that it returns a wrapper with raw package file data and documents missing/invalid parameter errors, but it omits authentication, permissions, and any file-size or binary-download behavior.

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 short and front-loads the action with a clear first sentence. The downstream Args/Returns/Raises blocks are mostly concise, though the '**kwargs' framing is slightly misleading given the explicit schema parameters.

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 16-parameter download tool with no output schema and 0% schema coverage, the description is too sparse. It mentions return data and some errors, but does not explain the majority of parameters or key download behavior, and it incorrectly implies required parameters that the schema marks optional.

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% across 16 parameters, and the description only names four example parameters (project_id, package_name, package_version, file_name). It does not explain the remaining parameters such as ref, status, package_type, package_id, page, per_page, or api_parameters, and it says those four are required even though the schema marks all parameters optional.

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 a specific verb ('Download') and resource ('repository package') scoped to a project. It implicitly distinguishes from siblings like get_repository_packages (list) and download_release_asset (release asset), though it does not explicitly name alternatives.

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 implies the use case: downloading a package file for a given project, package name, version, and file name. However, it gives no explicit guidance on when to use this instead of related tools such as get_repository_packages or download_release_asset.

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