send_bark_notification

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

With no annotations, the description carries full burden. It describes sending notifications and urgency levels, but does not disclose error handling, rate limits, or potential side effects (e.g., if ciphertext is provided). It mentions encryption only in passing. 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 concise, using a single paragraph with clear enumeration of use cases and level guidance. Every sentence adds value with no fluff.

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 13 parameters (all documented in schema) and no output schema, the description covers the main functionality and usage. It does not explain return values or error handling, but for a notification tool this is acceptable. Context is reasonably 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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining when to use each 'level' enum (critical for urgent, timeSensitive for important updates, etc.), which goes beyond the schema's description. Other parameters repeat schema info, so this extra context justifies a 4.

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 'Send a push notification via Bark to an iOS device', providing a specific verb and resource. It distinguishes from siblings (check_bark_server_health, send_bark_batch_notifications) by focusing on single push notifications.

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 explicitly lists five scenarios when to use the tool (task completion, errors, user input needed, testing, long-running operations). It also provides guidance on choosing the 'level' based on urgency, though it does not explicitly state when not to use (e.g., for batch sends or health checks).

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