Find class sections in a term (WebSoc)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description goes beyond these by noting it queries the 'live schedule,' requiring at least one narrowing filter, and summarizing the returned section data. There is no contradiction between the description and the annotations.

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 compact: three sentences convey what the tool does, what it returns, how it can be filtered, and the required-filter rule. Key information is front-loaded, and every sentence earns its place.

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?

With 21 parameters and no output schema, the description handles selection context well by naming primary return fields and the mandatory narrowing constraint. Per-parameter semantics are fully covered by the schema, so this is a solid overall package. Minor gaps remain around pagination and output volume, but the schema's `limit` description partially addresses this.

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?

All 21 parameters have schema descriptions, so the baseline is 3. The description names broad filter categories such as department, course number, GE, instructor, days, and time window, but it does not add detail beyond the schema, such as dependencies between avoidDays/avoidStart/avoidEnd or the default limit behavior.

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 opens with 'The main course-finding tool' and states that it queries UCI's live schedule for a term and returns matching sections with meeting times, instructor, location, seats, waitlist, and final exam. This is a clear verb-resource pairing with a specific resource and scope. It does not explicitly contrast itself with sibling search_courses, so it is just short of a 5.

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 provides clear context for when to use it—finding course sections in a term—and explicitly states a hard precondition: 'At least one narrowing filter besides the term is required.' It also enumerates the dimensions an agent can filter by. However, it does not name alternative tools or state explicit when-not-to-use conditions.

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