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

With no annotations, the description carries the full behavioral burden. It discloses scope ('across all accessible boards') and that the digest is computed on demand, plus the categories returned, but says nothing about auth requirements, cost, or whether results are cached. Adequate for a low-risk read, but not rich.

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 tightly written sentences: the first front-loads what the tool produces, the second gives the trigger questions. No filler or restated structured data.

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-parameter read tool with no output schema, the description usefully enumerates the digest sections, giving the agent a sense of the return shape. It is essentially complete, missing only explicit return-format details, which is minor here.

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 tool takes zero parameters, so the baseline of 4 applies. There is no parameter syntax to clarify, and the description correctly adds nothing that would be redundant.

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?

States a specific verb (compute) and resource (on-demand digest of the calling user's tasks) and enumerates the digest contents (overdue, stale, new assignments, open count, recently completed). Very clear, though it does not explicitly differentiate itself from the sibling 'my_work', which appears to overlap.

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?

Provides concrete usage context via example questions ('what needs my attention?', 'what's my work summary?'), which effectively tells the agent when to reach for this tool. It stops short of naming when-not to use it or pointing to alternatives like my_work or list_tasks.

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