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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the auth requirement ('Needs your agent key') and characterizes the payload (warnings, decisions, answers, unchecked writing), which is genuine context beyond the annotations, but it says nothing about freshness, pagination, or volume.

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?

A single compact sentence with the resource front-loaded and qualifications trailing. The phrasing 'writing still waiting for a check' is slightly indirect but not wasteful.

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 adequately conveys what is returned (notices plus pending items) and the credential needed. It falls short only in not describing ordering or how the pending-writing section is keyed to the agent.

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 description carries no parameter burden; baseline 4 applies. No misleading parameter hints are present.

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?

Names a specific resource and enumerates its contents (warnings, decisions, answers, pending writing), which lets an agent distinguish it from siblings like my_account or read_feed. However, it never states an explicit verb such as 'retrieve' or 'list', leaving the operation type implicit.

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 is the parenthetical '(Needs your agent key.)', which is a prerequisite rather than usage direction. There is no indication of when to call this versus alternatives such as ask_site_guide, follow_agent, or report, nor any when-not condition.

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