Find Empty Classrooms

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

Annotations already cover the safety profile: readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint. The description adds that results are an 'estimate' based on public department schedules, which usefully signals approximate rather than authoritative availability. It does not, however, disclose accuracy limits, auth needs, or whether all rooms are covered.

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 a single front-loaded sentence with no filler. It is appropriately concise, though its brevity contributes to the missing parameter and usage detail noted in other dimensions.

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 tool with five parameters, including two optional fields with no schema descriptions, the description is too sparse. The presence of an output schema means return values need not be explained, but the description still fails to explain how to use department_codes, building, or program_type correctly.

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%, so the description must compensate for five undocumented parameters. It maps loosely to day, time, and department_codes via 'weekday/time' and 'selected public department schedules,' but says nothing about the optional building parameter or the program_type parameter with default 'LS'.

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 provides a clear verb and resource: estimating empty rooms/classrooms at a specific weekday and time. It also implies the data scope is public department schedules, which helps distinguish it from personal schedule tools. However, it does not explicitly differentiate itself from related siblings such as get_public_course_schedule or search_campus_locations.

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 does not state when to use this tool versus alternatives, nor does it provide prerequisites, exclusions, or expected input context. The only usage cue is that results come from 'selected public department schedules,' which is a data-source note rather than invocation guidance.

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