getActiveSessionTimes

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get active session availability times' without explaining filtering semantics, output format, pagination, or any side effects. This is a significant gap for a tool that queries time availability.

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 short sentence, so it is concise in size, but it is under-specified and fails to provide meaningful information beyond the tool name. It is not wastefully verbose, but it does not earn its place by adding substance.

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 5 parameters, no annotations, and no output schema, the tool requires more descriptive context to be usable. The one-sentence description does not explain how the parameters interact (e.g., whether days and times are filters or inputs), and the large sibling list makes the lack of guidance even more problematic.

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 80% (4 out of 5 parameters have descriptions). The description itself adds no parameter semantics beyond the schema, and the undocumented `scheduleType` parameter relies solely on its enum values. This matches the baseline of 3 for high schema coverage.

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 verb 'Get' and resource 'active session availability times', which is specific enough to indicate the tool's basic function. However, it does not distinguish this from sibling tools like getScheduleItems or getClassSchedules, so it loses some points for lack of differentiation.

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 on when to use this tool versus alternatives. With many sibling tools like getScheduleItems, getBookableItems, and getClassSchedules, the lack of any contextual usage instructions makes it difficult for an agent to choose correctly.

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