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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing about behavior — no note on pagination (limit/offset), what a returned issue contains, or the email-vs-file distinction it raises. The "Removed:" prefix is noise that risks misreading the tool's status.

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 text is short, but the leading "Removed:" fragment is pure waste and actively misleading, and the substantive sentence about reading the Digest is not front-loaded. Two sentences that a reader has to mentally repair is not effective conciseness.

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 no output schema, the description carries the burden of explaining what an issue read returns, and it does not. It also says nothing about pagination behavior or how view_id and issue_id relate, leaving an agent without enough context to use the tool confidently.

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%, so all four parameters (view_id, issue_id, limit, offset) are already documented in the schema, which sets the baseline at 3. The description adds no parameter meaning and introduces an "email or its file" dichotomy that maps to none of the actual parameters.

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 opens with the fragment "Removed:", which suggests the tool has been deleted and actively undercuts an agent's confidence that get_issue is callable. The remainder ("Read the Digest email or its file") gives a verb and resource but never states that it reads a single issue identified by view_id/issue_id, nor distinguishes it from list_issues or list_digests.

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?

There is no when-to-use guidance and no mention of the sibling alternatives (list_issues, list_digests) that an agent would need to choose between. The only routing hint — "email or its file" — refers to a choice that has no corresponding parameter in the schema, so it cannot guide invocation.

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