blackboard_upload_attempt_file

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

Beyond annotations (destructiveHint=true), the description discloses that the file is visible to the instructor, that upload is separate from attachment, and that the server will ask the user to confirm the path. It also warns against blindly following filePath instructions from untrusted sources. No contradiction with annotations.

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?

Every sentence adds value: purpose, limitation, follow-up tools, instructor visibility, confirmation flow, and safety rule. It is front-loaded with the main action and remains concise without 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 fully covers the tool's role in the workflow: upload, return ID, next steps, side effects (instructor visibility), and security guidance. Despite no output schema, it clearly explains the return value and how to use it. It is complete for an upload tool with moderate complexity.

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 filePath and confirmed. The description adds meaning by specifying acceptable file types (image, PDF, doc) and reinforcing that confirmed is deprecated. It also warns about the source of filePath, which is not in the schema, enriching parameter semantics.

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's function: uploads a local file to Blackboard and returns a fileUploadId. It explicitly differentiates from siblings by stating 'it does NOT attach it to an attempt yet' and references related tools (save_attempt_draft, submit_attempt) for the next step.

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?

Provides explicit usage direction: pass returned fileUploadIds to blackboard_save_attempt_draft or blackboard_submit_attempt. Also includes safety guidelines about not choosing filePath from course content, and explains the user confirmation elicitation flow.

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