get_today_items

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

Even with readOnlyHint=true and openWorldHint=false, the description adds substantial behavioral context: items earlier than the date are included, deadline-only tasks are excluded, timezone behavior is specified, recurring-task generation caveats are disclosed, and known testing limitations are noted. This goes well beyond the annotations.

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 core behavior is front-loaded in the first sentence, with clarifying edge cases and caveats following. It is slightly verbose with dated observations and testing notes, but those notes are informative and not redundant fluff.

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 and an output schema, the description is highly complete: it covers timezone resolution, scheduling semantics, exclusions, known recurring-task behavior, and testing caveats. Nothing essential is left unstated.

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 schema already describes the only parameter with full coverage, including its format, default behavior, and day <= date semantics. The description restates these details rather than adding new parameter-level meaning, so the baseline of 3 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 opens with a specific verb and resource: 'Get open tasks and projects scheduled today or earlier.' It clearly distinguishes this tool from get_due_items by stating that deadline-only tasks are excluded and belong to that sibling tool.

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 tells the agent exactly what this tool is for and when not to use it: tasks with only a deadline are not included and should be fetched with get_due_items. It also describes the date-filtering behavior precisely (day <= date), leaving little to inference.

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