Get Homework Vaults

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the returned payload content, notably that direct upload URLs come back, which is a meaningful trait for an agent about to upload. However, it says nothing about authentication/session prerequisites (relevant given the check_auth_status and set_session_cookies siblings), whether upload URLs expire, or whether the listing is paginated or complete.

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?

A single front-loaded sentence with no filler; the highest-value elements (vaults, instructions, upload URLs) appear immediately after the verb. Nothing would be lost by leaving it as is.

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 tool is simple (one required parameter) and the output schema already documents return values, so the description needn't explain them. Still missing is the operational context an unannotated tool should provide: that a valid session is required and how this relates to the submit_homework_file sibling.

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 course_code, faculty, and semester are already documented with defaults and an example format. The description adds only the implicit "for a course" scoping and no extra semantics for the faculty or semester slugs, so the baseline 3 applies.

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?

Uses a specific verb ("List") with the resource spelled out in three parts: homework submission vaults (odevzdávárny), assignment instructions, and direct upload URLs, scoped to a course. The Czech term in parentheses helps an agent match local terminology. It stops short of explicitly differentiating itself from submit_homework_file, the adjacent write-side sibling.

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?

There is no when-to-use guidance, no mention of prerequisites, and no named alternative. An agent must infer that this is the discovery step before calling submit_homework_file, and that it applies only to homework-type vaults versus other course resources.

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