search_classes

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Search for OSU classes', implying a read-only operation but fails to mention pagination, result format, default behavior (e.g., current term), or any rate limits. This is inadequate for a tool with 10 parameters.

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 very concise (one sentence) and front-loaded with the core purpose. However, it is structurally flat and lacks any separation of usage notes, which limits its utility for an agent.

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 the high parameter count (10) and no output schema, the description should elaborate on search semantics (e.g., logical OR, wildcards), term code format, and result set size. It provides none of this, leaving the agent underinformed.

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 coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; 'by keyword, subject, instructor, etc.' is a high-level summary that doesn't explain parameter interplay or typical use patterns.

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 states 'Search for OSU classes' with a clear verb-resource pair. It mentions several search dimensions (keyword, subject, instructor), but the trailing 'etc.' is vague, reducing precision. Still, the core purpose is obvious.

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?

No guidance provided on when to use this tool versus alternatives. There are no sibling tools for classes, so confusion is unlikely, but the description doesn't clarify scope (e.g., current vs. all terms) or state that it returns a list.

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