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

Annotations already declare readOnlyHint and destructiveHint=false, so the description's job is extra context, and it delivers: sort order (overdue first, finished newest first), one call is one page, file URLs expire in ten minutes and never carry contents, and a syncedAt caveat about cloud freshness. It stops short of stating limits or what happens at page boundaries beyond the offset rule.

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 purpose is front-loaded, but the body is a dense run-on chain of em-dash clauses that mixes return fields, pagination, and freshness caveats without paragraph breaks. Each clause carries information, yet the packaging makes it slower to parse than it needs to be.

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 nine optional parameters and no output schema, the description carries the entire burden of explaining returns, and it does: field-by-field coverage of lastRun, goal, isGoal, files, agentNote, plus ordering, pagination, and cloud sync state. Nothing an agent needs to call this correctly appears to be missing.

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 coverage is 100%, so every parameter is already documented, and most of what the description says about since/offset largely restates the schema's own wording about "cursor" and "nextOffset". The one genuinely additive note is that an unscoped listing also answers "agents", which is return-shape context rather than parameter meaning. Baseline 3 fits.

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?

"Reads tasks from the Offhand to-do list" gives a specific verb and resource, and the whole description stays in read territory, which cleanly separates it from the write-oriented siblings add_task and set_task_status. An agent knows immediately this is the retrieval path rather than a mutation.

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?

It gives real conditional guidance: use since for a scheduled check ("nothing new answers with no tasks"), use task to follow handed-out work, and a listing without since or task also returns "agents". It never explicitly names the siblings or states when not to use it, but the routing signals are concrete rather than implied.

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