get_overdue_tasks

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

With no annotations provided, the description carries the full burden. It states the basic read operation but does not disclose behavior such as scope (all users or current user), sorting, pagination, or permissions. The description is minimal and lacks context beyond the core functionality.

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 wasted words. It is front-loaded with the action and includes the exact filtering criteria, making it highly concise and structured.

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 zero-parameter read tool, the description covers the basic action, but it omits context about the scope of 'all tasks' and what the return format might be. Since there is no output schema and no annotations, some ambiguity remains, though the description is not severely incomplete.

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 tool has zero parameters, and the description fully captures what is needed. There is no additional parameter information to provide, so the baseline score of 4 applies.

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 all tasks that are past their due date and not completed' with a specific verb and resource, and the scope is well-defined. This distinguishes it from siblings such as list_tasks_by_user (user-filtered) and search_tasks (broad search).

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 usage is implied by the description: use this tool when you need overdue tasks. However, there is no explicit guidance on when not to use it or how it compares to alternatives like list_tasks_by_user or search_tasks.

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