send_ntfy_notification

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

Annotations already declare the tool as non-readOnly, idempotent, and non-destructive. The description adds valuable context about the required NTFY_BASE_URL and optional auth token, and explains the behavioral differences between priority levels (e.g., sound, screen on). This goes beyond annotation information.

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 composed of four concise sentences, with the main action stated first, followed by structured lists for topics and priorities, and ending with a requirement note. There is no redundant information.

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 tool's side-effect nature and lack of output schema, the description adequately covers inputs and behavior. It could mention potential errors (e.g., invalid topic) or delivery confirmations, but the provided context is sufficient for typical use.

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 schema describes tags, title, message, and click_url, but lacks descriptions for 'topic' and 'priority'. The description compensates by explaining the meaning of each topic (e.g., 'risk' for circuit breaker) and each priority level (e.g., 'max/urgent' with screen on). This adds significant semantic value beyond the enum values.

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 mobile push notification via ntfy', providing a specific verb and resource. It also lists the distinct topic categories and priority levels, which differentiates this tool from other notification tools like email or SMS.

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 clear guidance on when to use each topic (e.g., 'bots' for trade notifications) and priority levels (e.g., 'max/urgent' for always-on screen). It also mentions the prerequisite environment variables. However, it does not explicitly state when not to use this tool or suggest alternatives.

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