search_courses

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

Discloses that the tool performs a real-time query against a specific API, describes the return structure, and notes that remain_url requires a separate action. No annotations are provided, so the description carries the burden, and it does so adequately without contradictions.

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?

Well-structured with a header, parameter list, and return format. Uses bullet points for readability. Slightly verbose but every sentence adds value.

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?

Covers all important aspects: parameters, return structure, and related tool. Lacks edge-case handling (e.g., error scenarios) but is sufficient for effective use.

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?

Despite 0% schema description coverage, the description compensates by detailing each parameter with format and examples (e.g., semester format '1151', dept examples '財務管理學系' or '357', keyword optional). Adds meaning beyond the schema.

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 verb (查/查詢), resource (開課清單/courses), and scope (by department and semester). It explicitly references the API source and distinguishes from sibling tools like list_departments for department code lookup.

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 guidance on how to use parameters: semester format, dept as name or code, and keyword as optional. Directs the user to list_departments for code lookup. Does not specify when to avoid using this tool, but the context is clear.

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