bos_notifications

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

The description only states 'Get', implying a read operation, but does not disclose any behavioral traits such as idempotency, authentication requirements, pagination behavior, or result ordering. With no annotations provided, the description carries the full burden, which it fails to meet.

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 with a single sentence, but it is too minimal. It could be expanded to include parameter details or behavioral notes without being verbose.

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 low schema coverage (0%) and no output schema, the description is incomplete. It does not clarify what 'notifications' are returned, ordering, pagination limits, or the effect of the unread_only parameter. The tool is simple, but the description still lacks essential context.

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?

The input schema has 0% description coverage, and the tool description does not explain any parameters (page, unread_only). It adds no meaning beyond the schema's property names, leaving the agent to guess their purpose.

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 'Get user notifications' clearly specifies the action (get) and resource (user notifications). It distinguishes itself from sibling tools like bos_notification_mark_read, but lacks scope details such as whether it returns all notifications or only for the current user.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that this is for listing notifications, nor does it differentiate from related tools like bos_notification_mark_read.

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