Get Course Class Files

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

No annotations provided, so the description bears full responsibility. It only states 'list files and folders', implying a read operation, but lacks any additional behavioral context (e.g., authentication needs, rate limits, or that it is non-destructive).

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?

Extremely concise (single sentence, 13 words). While efficient, the brevity sacrifices necessary details, especially for parameters. It is not bloated but could be more informative without losing conciseness.

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 tool has 4 parameters and no annotations or schema descriptions, the description is insufficient. It covers only the basic purpose, leaving out parameter usage, behavioral details, and usage context.

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 0%, so the description must explain parameters. It does not mention 'course', 'compact', 'max_depth', or 'recursive' at all. The parameter names provide some hint, but no explicit meaning is added.

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 action ('List'), resource ('files and folders'), location ('Ninova 'Sınıf Dosyaları' section'), and scope ('for a course'). It is specific and differentiates from sibling tools like get_course_lesson_files.

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?

No guidance on when to use this tool versus alternatives. With siblings like get_course_lesson_files, the description should clarify the differences but does not.

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