Уведомления

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds specific notification types but does not disclose additional behaviors like pagination or response format. With annotations covering the safety profile, the description provides moderate added value.

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 a single concise sentence, front-loaded with the subject and specific notification types. No unnecessary words or repetition; it is maximally efficient.

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 simple list tool with two parameters and no output schema, the description is adequate. It states what notifications are included, and the schema covers pagination and filtering. Annotations handle the read-only nature, so 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?

Both parameters (limit and unread_only) are fully described in the schema with clear meaning and defaults. The description adds no extra semantic detail beyond the schema, which already carries the heavy lifting.

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 resource (account notifications) and enumerates the specific categories (invitations, role changes, budget thresholds, bank payments). The verb 'list' is implicit in the tool name and the description's scope, and it distinguishes from siblings like notifications_read which likely marks as read.

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?

Usage is implied by the description, but there is no explicit guidance on when to use this tool versus alternatives such as notifications_read or other list tools. The description gives context on what it returns but does not state exclusionary conditions.

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