get_due_items

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

No annotations provided, so description must disclose behavior. It only states what tasks are returned, but omits details like sorting, pagination, read-only nature, auth needs, or effects. Minimal disclosure.

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 direct sentences: first declares purpose, second provides usage context and an alternative. No extraneous words.

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?

Core functionality is clear, but parameter semantics are missing and behavioral transparency is low. Output schema exists, so return values need not be described, but the description lacks sufficient context for the single parameter and behavioral expectations.

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 has one optional boolean parameter 'debug', but the description does not mention it or explain its effect. With 0% schema description coverage, the description fails to add meaning beyond the schema.

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?

Description clearly states the tool gets overdue and due tasks only, specifying 'past due date'. It distinguishes from sibling tool get_daily_productivity_overview by contrasting focus on urgent items versus a complete daily view.

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 says when to use (focus on urgent/overdue items) and provides an alternative for a complete daily view. Does not cover other siblings like get_all_tasks, but the given guidance is clear.

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