notion_get_overdue_tasks

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

Annotations already establish that this is a safe read operation. The description adds meaningful behavioral detail by specifying the two inclusion paths (explicitly Overdue, or past due without Done/Archived/Overdue status) and the return shape as a JSON array. It goes beyond what annotations alone convey.

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 concise and front-loaded: the first line states the action and resource, and the second defines the boundary conditions. Every sentence adds useful information with no filler or redundancy.

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 that the tool has no parameters, an output schema exists, and annotations cover the read-only behavior, the description is complete. It clearly defines the task selection criteria and the return format, so an agent can invoke it correctly without further clarification.

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?

There are no parameters, and the schema is fully described with zero properties, so the description has no parameter burden. The baseline for zero-parameter tools is 4, and the description appropriately focuses on behavior and output instead of parameters.

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 operation ('Return all overdue tasks') and the exact resource (overdue tasks in Notion). It also defines precisely what counts as overdue, which distinguishes it from a generic fetch like notion_get_tasks. The nuance about excluded statuses removes ambiguity.

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 implies the use case: retrieving overdue tasks rather than all tasks. However, it does not explicitly mention alternatives such as notion_get_tasks or give conditions for when to prefer this tool. The selection criteria are clear, but no explicit routing guidance is provided.

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