OBS Course Prerequisites

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

No annotations provided, so description carries full burden. It discloses a behavioral trait: chain queries up to 10 levels deep. However, it omits other traits like read-only nature, rate limits, or data freshness.

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 concise sentences with no wasted words. Purpose is front-loaded, and key feature (chain depth) is included.

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?

For a query tool with an output schema (present), the description is fairly complete: states resource, relationships, and depth limit. Missing details like direction default and depth range, but output schema may cover return structure.

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 0%. The description hints at 'course_code' and 'direction' (prerequisite/postrequisite) and 'max_depth' (up to 10 levels), but does not fully explain defaults or allowed values. Minimal added value over schema names.

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?

Description clearly states the tool queries prerequisite/postrequisite relationships for a course from the OBS public catalog, and distinguishes itself with chain query support. The verb 'query' and resource 'OBS public catalog' are specific.

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?

Description implies usage for exploring course relationships but does not explicitly state when to use vs. alternatives like get_public_course_prerequisites or other course info tools. No exclusions or when-not guidance.

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