list_schedules

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

No annotations provided, so description carries full burden. Discloses auth requirement and return fields. Adequately indicates it is a read-only operation without destructive effects, though not explicitly stating it is safe.

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?

Two concise sentences with no wasted words. Front-loaded purpose, followed by return value and usefulness. Highly efficient.

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 parameters and presence of output schema, the description fully covers what an agent needs: action, auth requirement, return fields, and practical follow-ups. No gaps identified.

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?

Input schema has zero parameters (coverage 100%), so the description need not explain parameters. Baseline 4 is appropriate; no additional param semantics needed.

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?

Clearly states 'List the saved schedules' and specifies the returned fields (id, name, semester, section ids). Distinguishes from sibling tools like save_schedule and delete_schedule by mentioning its use for finding a schedule_id to update or delete.

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?

Explicitly requires authentication. Contextually guides usage by noting it returns schedule IDs for subsequent update/delete operations. Does not explicitly state when not to use, but sibling names imply clear boundaries.

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