Get Syllabus

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is fully covered. The description adds that the return is structured, but discloses nothing extra about auth needs, rate limits, or failure behavior; a 3 is appropriate with annotations doing the heavy lifting.

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 tightly packed sentences with no waste: purpose first, then the sourcing instruction for inputs. Fully front-loaded and appropriately sized.

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?

An output schema exists, so return structure needn't be explained, and annotations cover the safety profile. The description covers purpose and where to source inputs, which is sufficient for a detail-fetch tool, though the undocumented parameters remain unexplained.

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 low (33%): only clssno1 and sbjtno1 carry field labels, while year, term, sust and campcd are undocumented. The description partially compensates by telling the agent the values come from the eclass_search_syllabus result row, but adds no per-field meaning for the undocumented parameters.

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 and resource (returns a specific course's structured syllabus body) and enumerates the returned content (textbook, evaluation ratios, weekly schedule, professor info). It also implicitly differentiates from sibling eclass_search_syllabus by telling the agent to feed this tool that sibling's result rows.

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?

Gives a clear workflow instruction: take the input keys directly from an eclass_search_syllabus result row. This tells the agent when/how this tool is used (detail fetch after a search), but there are no explicit exclusions or when-not-to-use conditions.

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