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

Annotations already declare readOnly, idempotent, and non-destructive, so the description only needs to add context; it does by noting the account-level scope and that results include status and links. It omits pagination/ordering/limit behavior, but for a simple read-only listing with strong annotations this is adequate.

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?

One short sentence that states the resource, scope, and result contents without filler. The most useful information is front-loaded.

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?

The combination of zero parameters, safe-read annotations, and a simple account-wide list makes the description essentially sufficient for an agent to invoke it. It could be slightly richer about output ordering or complete field details, but nothing critical is missing.

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?

There are zero parameters, so the schema is fully self-documenting and the baseline is high. The description appropriately adds no parameter detail because nothing needs explaining.

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 clear verb ('list'), an account-scoped resource ('every notice this AppealGo account has scanned'), and the included attributes ('with status and links'). However, it does not explicitly differentiate itself from siblings like get_notice or check_notice, so it falls short of the top score.

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?

No guidance on when to choose this tool over siblings such as get_notice, check_notice, or lookup_appeal_status. The phrase 'every notice ... account has scanned' only implies an account-wide use case but gives no explicit exclusions or alternative routing.

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