OBS Search Courses

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

Discloses that no authentication is required, which is a key behavioral trait. However, does not mention rate limits, pagination, or what happens on no results. With no annotations, more detail would be beneficial.

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?

Single sentence, concise, front-loaded with verb and resource. Could be slightly more structured but is clear and efficient.

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?

Adequate for a simple tool with output schema present. Covers purpose and a behavioral trait, but lacks parameter details for limit. Overall sufficient but not thorough.

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?

The description mentions 'code or name' which relates to the query parameter, but does not explain format or that limit is available. With 0% schema description coverage, the description should provide more parameter guidance.

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?

Clearly states the verb 'search', resource 'public OBS course catalog', and criteria 'by code or name'. Distinguishes from sibling tools like list_courses or get_course_info which are for different purposes.

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?

Implicitly tells when to use: when searching by code or name. No explicit exclusions or alternatives, but the context of 'public' and 'no auth' sets it apart from authenticated course tools.

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