get_deadlines

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

Beyond the readOnly and openWorld annotations, the description discloses important behavior: timezone, date sorting, hiding completed items by default, hiding old overdue items unless configured, and possible partial results with a pending-course list. It does not fully describe the return shape, but it adds substantial operational context.

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 purpose is front-loaded and nearly every clause adds useful information about scope, sorting, filters, or partial results. The single dense paragraph is efficient but could be easier to scan with slightly more structure.

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 six-parameter read-only listing tool with no output schema, the description covers scope, defaults, filtering, timezone, sorting, and partial-result behavior. It is close to complete, though it could say more about the exact returned fields beyond status and days remaining.

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 coverage is 100%, so the schema already documents parameter formats and defaults. The description adds cross-parameter meaning, especially how course_id interacts with the active course profile and all_courses, and how include_completed and overdue_days affect visibility.

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 retrieval purpose: upcoming assignment submissions and quiz closings, for one or all courses, sorted by date. It is much more specific than the name alone, but it does not explicitly differentiate itself from siblings such as list_assignments or get_quiz_info.

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?

It gives clear context for when the default scope applies: without course_id it uses the active course profile or all courses, and all_courses forces all courses. It also explains filtering behavior for completed and overdue items, though it does not explicitly name when to use this instead of related assignment or quiz tools.

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