get_due_items

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

Annotations already declare readOnlyHint=true, so the read-only safety profile is covered. The description adds useful selection semantics (open items, deadline today or earlier), but it does not disclose additional behavioral traits such as ordering, pagination, or authentication requirements. No contradiction with annotations exists.

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, front-loaded sentence with no filler. Every word contributes to the meaning, and the core operation, resource, and constraint are immediately clear.

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 read-only tool with one optional parameter, an output schema, and full schema description coverage, the description is complete enough. An agent can determine what to call, what the parameter means, and what to expect in terms of safety without needing additional 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?

Schema description coverage is 100%: the single optional 'by' parameter is fully documented as an inclusive YYYY-MM-DD deadline, with omission meaning today. The description essentially restates this deadline concept without adding new parameter semantics 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 uses a specific verb ('Get') and resource ('open tasks and projects') with a precise deadline condition ('today or earlier'). It clearly conveys what the tool returns, though it does not explicitly differentiate itself from the similarly named sibling get_today_items.

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 intended usage is implied by the description: retrieve tasks/projects that are open and due by today or an earlier date. However, it provides no explicit when-to-use guidance, exclusions, or mention of alternatives such as get_today_items or get_done_items.

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