get-inbox-notification

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states this is a 'Get' operation (implying read-only), but doesn't disclose authentication requirements, rate limits, error conditions, or what happens if the notification doesn't exist. The description doesn't contradict annotations (none exist), but provides inadequate behavioral context.

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 5 words, front-loading the essential purpose with zero wasted language. Every word ('Get', 'Liveblocks', 'inbox', 'notification') contributes directly to understanding the tool's function.

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 2 required parameters, 0% schema coverage, no annotations, and no output schema, the description is severely incomplete. It provides basic purpose but lacks parameter explanations, usage context, behavioral details, and return value information that would be necessary for effective tool invocation.

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?

With 0% schema description coverage for both parameters (userId and inboxNotificationId), the description provides no parameter information whatsoever. It doesn't explain what these IDs represent, their format, where to obtain them, or their relationship. The description fails to compensate for the complete lack of schema documentation.

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 action ('Get') and resource ('Liveblocks inbox notification'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'get-inbox-notifications' (plural), which appears to retrieve multiple notifications versus this single-notification retrieval.

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. It doesn't mention the sibling 'get-inbox-notifications' for retrieving multiple notifications, nor does it explain prerequisites like needing specific notification IDs or user contexts.

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