send_notification

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

Discloses key behavior: automatic emoji prepending, default emojis by event type, and icon override. No annotations are provided, so description carries full burden; it does a good job describing the tool's operation without contradictions.

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?

Concise yet comprehensive. Uses bullet points for default emojis and examples. Every sentence adds value; no fluff or repetition.

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 4 parameters, no annotations, and presence of output schema, the description covers all necessary behavioral and parameter information. It is fully complete for an agent to invoke 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 coverage is 0%, but the description fully explains each parameter: event (enum values listed), summary (one-line, ≤200 chars), details (multi-line), icon (optional override). Adds meaningful context beyond schema structure.

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?

Clearly states the action (send) and resource (structured notification to Telegram chat). Distinguishes from siblings by specifying that it sends a structured notification with automatic emoji prepending, unlike send_message (presumably plain) or send_notification_with_buttons (interactive).

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?

Provides examples of when to override icons (deployment, test run, report) but does not explicitly guide when to use this tool versus siblings like send_message or wait_for_reply. Implicit usage is clear but lacks exclusions.

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