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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful scope context ('calling user's tasks', 'across all accessible boards', computed on demand), but says nothing about cost, aggregation limits, or how large result sets are handled. Under annotation coverage the added value is modest.

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 sentences with no filler, front-loading the operation and scope, followed by intent examples. Every clause carries information the agent can use.

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 zero-param read tool with rich annotations and no output schema, the enumerated digest sections stand in for a return-value description, which is nearly sufficient. A brief note on how 'stale' is defined or on result volume would close the remaining gap.

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?

Zero parameters, so there is no schema semantics to explain; baseline 4 applies. The description correctly implies no filtering inputs by framing the result as the caller's own digest.

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?

Specific verb 'compute ... digest' with an explicit resource scope: the calling user's tasks across all accessible boards. It also enumerates the digest sections (overdue, stale, new assignments, open count, recently completed), which makes the output concept concrete. It stops short of naming the closest sibling (my_work) so the agent must still infer the distinction.

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?

Gives a clear usage context with two sample questions ('what needs my attention?', 'what's my work summary?'), which maps well onto realistic agent intents. No explicit when-not or named alternatives, so the agent is not told when to prefer my_work or list_tasks instead.

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