buddypress_list_notifications

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'List notifications' implies a read-only operation but doesn't specify authentication requirements, rate limits, pagination behavior (beyond what's in schema), return format, or whether it's safe to call repeatedly. For a tool with zero annotation coverage, this is inadequate.

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 extremely concise at just two words. While it's under-specified, it's not verbose or poorly structured. Every word earns its place, and there's no wasted text.

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?

Given the complexity (list operation with 4 parameters), no annotations, and no output schema, the description is incomplete. It doesn't explain what notifications are, how they're structured, what the return format looks like, or any behavioral considerations. For a tool in this context, more information is needed.

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 all parameters are documented in the schema. The description adds no additional meaning about parameters beyond what the schema provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'List notifications' is a tautology that restates the tool name 'buddypress_list_notifications'. It doesn't specify what kind of notifications (e.g., BuddyPress social notifications), what resource they belong to, or how this differs from sibling tools like 'buddypress_get_notification' (singular vs. list). The purpose is minimally stated but lacks differentiation.

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 description provides no guidance on when to use this tool versus alternatives. There are multiple related tools like 'buddypress_get_notification' (singular), 'buddypress_update_notification', and 'buddypress_delete_notification', but the description offers no context about when this list operation is appropriate versus those other operations.

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