getClassSchedules

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

There are no annotations, so the description carries the full burden. It merely says 'Get' with no disclosure of response format, behavior when no filters are provided, or read-only guarantees. This is minimal behavioral transparency for a tool with no output 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 a single, front-loaded sentence with zero fluff. It is appropriately concise, although it may be too terse to serve as a standalone guide.

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 no annotations, the seven-word description is insufficient for an agent to understand return values, filter semantics, or when this tool is the best choice among many sibling schedule-related tools. The parenthetical adds some clarity but leaves significant gaps.

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 fully documents all four parameters (staffIds, programIds, locationIds, classDescriptionIds) with explicit descriptions, so the description adds no additional meaning. Baseline 3 applies because schema coverage is 100%.

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 'Get class schedules' with a clarifying parenthetical '(recurring class templates)' that distinguishes it from sibling tools like getClasses (actual class instances) and getClassDescriptions. It names a specific resource and verb, though it doesn't explicitly reference alternatives.

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 is provided about when to use this tool versus related siblings such as getClasses or getScheduleItems. There is no mention of filter combinations or whether all options are optional, leaving the agent to infer usage solely from the schema.

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