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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety needs no elaboration. Instead of adding behavioral context, the description inserts a 'Removed:' claim that implies the tool is unavailable, which is misleading for a live callable read endpoint and contributes nothing about pagination or return shape.

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 short, but brevity here reflects under-specification rather than economy. The front-loaded 'Removed:' is misleading and the following sentence does not earn its place by clarifying the tool's function.

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 three-parameter list tool with no output schema, the description should at minimum explain the resource being listed and how results are scoped. It provides none of that, leaving the agent with no usable context beyond the title and schema.

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%, and all three parameters (limit, before, view_id) are individually documented in the schema. The description adds no parameter meaning whatsoever, 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 never states what the tool does. Instead of a verb+resource for listing a View's Digest Issues, it leads with 'Removed:' and then talks about the Digest being an email and a file, which is misleading rather than descriptive. An agent cannot tell from this text that the tool lists issues.

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 only guidance offered is 'Read the Digest email or its file,' which steers the agent toward non-tool behavior instead of explaining when to call list_issues versus siblings like get_issue or list_digests. No preconditions, no exclusions, and the 'Removed' framing actively discourages use.

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