notification-createNtfy

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

Annotations provide openWorldHint: true, indicating non-read-only behavior, but description adds no further behavioral details. No mention of side effects, authentication needs, or what gets created. Barely minimal.

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?

Description is extremely short but at the expense of substance. Not front-loaded with useful information; just the endpoint path. Lacks any structure to convey purpose or parameters.

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 complexity (12 required params, no schema descriptions, no output schema), the description provides virtually no context. Agent cannot determine tool's purpose or how to invoke it correctly.

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 description coverage is 0% and description does not explain any of the 12 required parameters. Agent must infer semantics from parameter names alone (e.g., appBuildError, serverUrl), which is insufficient.

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?

Description is just 'POST /notification.createNtfy' – repeats the endpoint path without stating what the tool does. Fails to specify verb+resource or distinguish from sibling notification creation tools (e.g., notification-createDiscord, notification-createSlack).

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 on when to use this tool vs alternatives. Sibling tools include many other notification creation methods, but no mention of selection criteria or context.

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