download_comses_model

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It extensively details safety guarantees: version resolution before cache path, HEAD request for size, stream byte cap, zip traversal validation, uncompressed size check, atomic move with marker. This goes well beyond basic transparency.

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 well-structured with a clear purpose statement, usage guidance, and bulleted safety guarantees. It is front-loaded but somewhat lengthy; however, the detail is justified by the tool's complexity. A slight reduction would not harm clarity.

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 the presence of an output schema (not needing return value explanation), the description covers all necessary aspects: purpose, usage guidance, parameter context implicitly, and extensive behavioral transparency. It is complete for the tool's complexity level.

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 100%, so baseline is 3. The description adds no additional semantics beyond what the schema provides for the three parameters (identifier, max_mb, version). The safety details relate to behavior, not parameter meaning.

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 and safely extract a COMSES model archive' and explicitly distinguishes itself from sibling 'open_comses_model' by noting it is a standalone 'fetch but don't open' tool. This provides a specific verb+resource and differentiates from 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 explicitly guides the agent: 'Most AI flows should use open_comses_model instead — it subsumes this tool and also loads NetLogo models into the workspace.' This provides clear when-to-use and alternative guidance.

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