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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered without the description. Beyond that, the text adds no behavior: no pagination, ordering, filter scope, or volume expectations for a list endpoint. The pointer to describe_operation is the only 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 short but wastes half its length on a verbatim duplicate of the endpoint path. The one useful clause (describe_operation for native schemas) is buried after the repetition and the opaque operation ID hash.

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 list endpoint with an untyped free-form query object, no output schema, and no required parameters, the description should at minimum sketch what the query object accepts and what a response contains. It provides neither, offering only a redirect to describe_operation, which leaves the agent unable to call it correctly in one step.

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% and both parameters (a free-form `query` object with additionalProperties:{} and an empty `params` object) are entirely undocumented. The description does not compensate — it only defers to describe_operation rather than naming any accepted query keys, so an agent cannot construct a filtered call from either source without an extra step.

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 is literally the HTTP path repeated twice: "GET /api/notifications. GET /api/notifications." It restates the tool title rather than explaining what notifications are returned (current user's inbox? workspace-wide feed?) or how it differs from siblings like get_notifications_unread_count or get_notification_settings.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the closely related notification tools. The only routing hint is that describe_operation exposes native request schemas, which helps find parameters but says nothing about selecting this tool over alternatives.

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