rehydrate_genome_package

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

With no annotations, the description must disclose behavioral traits. It mentions that package_path can be a ZIP file or directory, but does not discuss errors, size implications, or side effects. The tool's read-write nature is not clarified.

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 concise with one functional sentence plus an argument definition. It front-loads the purpose but includes an 'Args:' section that is somewhat redundant with the schema. Still efficient.

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 tool with one parameter and an output schema, the description covers the essential: what it does and what input to provide. It does not elaborate on return values, but the output schema handles that. The context of sibling tools is understood.

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 explains that package_path is a path to a dehydrated ZIP file or its extracted directory, adding significant meaning beyond the schema's plain string type. This is crucial given 0% schema description coverage.

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 tool fetches full sequence files for a dehydrated genome package, using the verb 'fetch' and specifying the resource. This distinguishes it from sibling tools that handle downloads by accession or taxon, data formatting, or summaries.

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites (e.g., prior dehydration step), or exclusions. The description only states its basic function.

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