notify_bell

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

The description is straightforward about the action, but with no annotations, it could mention side effects, failure modes, or environment requirements. For a simple tool, it is adequate but not comprehensive.

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, clear sentence with a prefix category. Every word is necessary, and it is front-loaded with the action. 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?

For a parameterless tool, the description covers the core action. It could mention that the bell only works in terminal environments, but the return value is handled by the output schema. Almost complete.

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?

There are no parameters, so baseline is 4. The description adds no parameter details, but none are needed. It clarifies the tool's action without conflicting with the schema.

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 it rings the terminal bell to alert the user, using a specific verb and resource. It is distinct from sibling tools like notify_notify_desktop or notify_notify_file, which provide different notification methods.

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 like desktop or file notifications. It implies a terminal context but does not explicitly state usage conditions or prerequisites.

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