Get Dropbox Submissions

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

With no annotations, the description carries the full burden and does so richly: instructor/TA-only access, a graceful 'clear note' for student accounts, limit capping (default 100, max 1000), explicit truncation signaling, and the side effect that feedback is only fetched for the returned slice. These are real behavioral traits an agent needs.

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?

Front-loads the purpose, then sequencing, then access/behavioral and pagination constraints in tightly packed sentences. Every clause earns its place with no 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?

No output schema or annotations exist, yet the description covers access requirements, returned fields, the truncation/pagination model, and cross-tool sequencing. Nothing an agent needs to call it correctly is missing.

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 all five parameters (including activeOnly and ignoreFeedback semantics) are already documented in the schema. The description's limit note restates what the schema already says, so it adds little beyond the baseline.

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?

States a specific verb ('List') and resource ('every student's/group's submission to a dropbox folder') and enumerates the returned fields. It is clearly distinguishable from siblings like get_dropbox_user_submissions and get_dropbox_feedback, so an agent can select it without opening other schemas.

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?

Explicitly routes the agent: use get_dropbox_folders first to get folderId, and steers students to download_file / get_assignments for their own submission. Both the when-to-use and the when-not/alternative are named.

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