get_my_timetable

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It mentions the default 'today' behavior and implies read-only via 'Get', but does not state authentication requirements, potential rate limits, error behavior, or any side effects. The disclosure is minimal and insufficient for a full understanding.

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, clear sentence with no filler. It front-loads the purpose and includes key details (date format and default) efficiently, making it easy to parse.

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 two parameters, no output schema, and no annotations, the description must provide enough context for a correct call. It misses the subdomain parameter, return format, and any prerequisites. The description is too sparse to be adequate for a tool in this context.

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 schema has 0% description coverage, so the description must explain both parameters. It explains 'date_str' with format and default, but completely omits 'subdomain'. The description adds value for one parameter but fails to cover the other, leaving a significant gap.

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 a specific verb ('Get'), resource ('timetable'), and scope ('for the logged-in user'), and specifies the date format with a default. This distinguishes it from sibling tools like get_student_timetable or get_timetable, which imply other scopes, without needing to read their schemas.

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 context that this is the logged-in user's timetable, implying it is for the current session, but it does not explicitly mention when to use this over alternatives like get_student_timetable or get_timetable, nor any exclusions. The guidance is implied but not explicit.

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