Trigger an alert

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

Annotations indicate mutation (readOnlyHint=false) and open world effects. Description uses 'simulate' but does not disclose whether alerts are real or temporary, or what side effects occur beyond the immediate trigger.

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?

Two sentences covering purpose and usage, no redundant words. Front-loads the core action (simulate) and then provides actionable guidance.

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?

Instructs to check get_settings for alert options, filling a key knowledge gap. Lacks return value description but acceptable for a simulation tool with openWorldHint.

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 covers both parameters with descriptions. Description adds concrete examples for extraSettings (e.g., { 'username': 'lumia', 'bits': 1000 }), enhancing agent understanding.

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 it simulates platform alerts with specific examples (twitch-follower, youtube-superchat, etc.). Distinguishes from sibling tools like send_announcement or set_state.

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?

Explicitly instructs to use get_settings to see configured alerts, providing a necessary precondition. Does not list when not to use but context implies for testing.

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