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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral context beyond the word 'List' – no mention of pagination, default status (which appears in the schema as 'open'), or any filtering behavior. It fails to enrich the agent's understanding beyond what annotations already convey.

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 description is concise (one sentence) but under-specified. It is not front-loaded with important details – it simply repeats the tool name's purpose without elaboration. Conciseness should not come at the expense of necessary information.

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 tool with 4 parameters, an output schema, and a complex domain (notifications with various filters), the description is grossly inadequate. It does not explain what the tool returns, how parameters interact, or any special behavior. The presence of an output schema does not compensate for missing usage guidance.

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 schema has 4 parameters (limit, cursor, status, severity) with 0% description coverage. The description does not explain any of them, so an agent has no insight into their meaning or how they affect the listing. This is a critical failure since the description must compensate for the lack of schema descriptions.

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 states a clear verb ('List') and resource ('TaskTools notifications'), which distinguishes it from mutation tools like notifications_ack or notifications_resolve. However, it does not differentiate from other list-like notification tools such as notifications_summary or notifications_scan, so it is not fully distinctive.

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 is provided on when to use this tool versus alternatives. The description gives no context about selection criteria, such as when to use notifications_summary instead, or what scenarios this list is best suited for. This is a clear gap.

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