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

Annotations already establish the safe-read profile (readOnlyHint true, destructiveHint false, openWorldHint false, idempotentHint true). The description adds genuine extra context beyond that: results are computed in the caller's own timezone, are limited to the token's workspace, and that a token cannot enumerate every workspace. It does not mention pagination or result limits, so it is strong but not complete.

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?

It is a single dense sentence with the scope and bucket list front-loaded and no filler. The dash-delimited aside about workspaces is a bit crammed in, but nothing is wasted.

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?

With an output schema present, return shape need not be explained, and annotations cover the safety profile. The description supplies scope, timezone behavior, and the bucket taxonomy, which is enough for an agent to call it correctly; only the optional project filter goes unmentioned.

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% for the single optional 'project' parameter, so the schema already carries the meaning. The description adds nothing about the project filter, so this sits at the baseline rather than above it.

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 names the resource (the app's My Work buckets) and enumerates exactly what is returned (overdue, today, thisWeek, later, noDate), so an agent knows this is the personal to-do overview rather than a generic list. It implicitly separates itself from siblings like list_todos and timesheet by scoping to work assigned to the caller. It never states a crisp verb like 'list' or 'retrieve', which keeps it just short of 5.

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 framing 'the answer to what should I do now' hints at the use case, and the workspace restriction clarifies a boundary, but no alternative sibling is named and no when-not-to-use condition is given. It is implied usage rather than explicit routing guidance.

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