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

Annotations already declare readOnlyHint=true, and the description adds the filter behavior (pending flag) and the advisory nature of notices. This goes beyond the annotation to explain how results should be interpreted, though it omits details like pagination or ordering behavior.

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?

Three concise sentences with no redundancy. The core purpose is front-loaded, and the parameter hint and caveat are added efficiently. Every sentence earns its place.

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 read-only list tool with two optional parameters and no output schema, the description covers the main parameter and the semantic nature of the data. The missing explanation of 'after' is a minor gap, but the tool is otherwise adequately specified for correct invocation.

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 0%, so the description must explain parameters. It explains 'pending' clearly ('notices you have not acknowledged') but does not explain 'after', which is an integer with a minimum of 0, likely a timestamp or cursor. Without an explanation, an agent may guess incorrectly. The description partially compensates but not fully.

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 clearly states the verb 'Read' and the resource 'network-wide notices', distinguishing it from siblings like read_broadcast which likely targets a single notice. It also adds the functional detail of the pending flag, making the tool's purpose unambiguous.

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?

It explicitly describes the primary use case ('Set pending=true for notices you have not acknowledged') and adds important context about the nature of notices being suggestions, not instructions. However, it does not explicitly name alternative tools like read_broadcast for single-notice access, leaving some routing to inference.

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