search_courses

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

No annotations are provided, so the description carries the full burden. It describes the parameters (query, page, perpage) but does not disclose behavioral traits such as rate limits, behavior for empty queries, or default pagination behavior beyond the defaults in the schema.

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?

The description is extremely concise: one sentence stating the purpose followed by a clear parameter list. Every sentence is informative and there is no redundancy or fluff. Front-loaded with the core purpose.

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 no output schema and a simple search operation, the description covers the tool's purpose and parameters adequately. It could be improved by mentioning the return format (e.g., list of course objects) or any additional behavior, but it is sufficiently complete for a tool of this complexity.

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 input schema has 0% description coverage, but the tool description provides clear meanings for each parameter (e.g., 'query: search text', 'page: 0-indexed page', 'perpage: results per page (max 100)'). This adds value beyond the raw schema, though it lacks examples or constraints beyond max perpage.

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 tool searches the public course catalog by keyword, with a specific verb and resource. It distinguishes from siblings like list_my_courses (personal courses) and get_course_contents (within a course).

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?

The description tells what the tool does but does not explicitly state when to use it versus alternatives. For example, it does not mention that list_my_courses is for personal courses. Usage is implied but not clarified with exclusions.

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