ariel_get_notifications

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is established. The description adds context about what kinds of notifications are returned, but it does not mention ordering, pagination behavior, or whether fetching might affect read state. This is acceptable given the annotations.

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, front-loaded sentence that names the resource and its relevant categories with no filler. Every word contributes to understanding the tool's purpose.

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 read-only getter with three optional, fully described parameters and clear annotations, this description is mostly complete. Minor gaps remain: there is no output schema and no explicit statement about default limit or pagination behavior, but the schema already explains the cursor and limit constraints.

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 100%, so limit, cursor, and format are already documented at the schema level. The tool description adds no parameter-specific meaning beyond the notification-type scope, so the baseline 3 applies.

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 specific action and resource—'Get recent notifications'—and enumerates the content categories (likes, reposts, follows, mentions, replies). This makes the tool's purpose clear and distinguishable from sibling getters like ariel_get_timeline or ariel_get_unread_count.

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?

The phrase 'recent notifications' implies this tool is for reading notification activity, but the description provides no explicit guidance about when to choose it over related siblings such as ariel_get_unread_count or ariel_mark_notifications_read. No alternatives or exclusions are named.

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