Download a submitted assignment file

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds little beyond restating the download purpose. It does not mention return format, file packaging, size limitations, or other behavioral details, leaving the description carrying minimal extra weight.

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 short sentences, with the core action front-loaded and the prerequisite immediately following. Every word earns its place; there is no filler or redundancy.

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 plus high-coverage schema provides enough for an agent to select and invoke the tool correctly. The absence of an output schema and any return-format details is a minor gap given the straightforward download nature, but the invocation guidance is otherwise complete.

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 100% with descriptions for all three parameters. The description adds meaningful semantic value by telling the agent that attemptId and columnId are obtained from bb_get_grade_detail, explaining how to source them rather than just what they are.

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 and object: downloads files the student submitted with an assignment attempt. This clearly distinguishes it from sibling download tools like bb_download_file and bb_download_course_files by grounding it in the assignment-attempt context.

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 instructs the agent to call bb_get_grade_detail first to find the attemptId and columnId, which is directly actionable. It does not enumerate when not to use the tool versus alternatives, but the sequencing guidance is clear and useful.

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