madeonsol_coordination_alerts_create

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

Adds key behavioral details: ~1s latency, WebSocket delivery, HMAC-signed webhook, one-time return of webhook_secret. Annotations (readOnlyHint=false, destructiveHint=false) are consistent; description enhances transparency.

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?

Three sentences, each essential. First sentence states purpose, second describes triggers and delivery, third explains output handling. No wasted words.

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?

No output schema, but description explains key output (webhook_secret once) and behavior. Could mention error conditions or prerequisites, but adequate for creation tool.

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 has 100% coverage; description adds context about delivery modes and the one-time webhook_secret behavior, which are not in schema descriptions. Adds value beyond schema.

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?

Clear verb+resource: 'Create a coordination alert rule'. Immediately distinguishes from sibling tools like delete, get, list, update.

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?

Describes when to use (creation) and provides details on delivery modes, but not explicit exclusions or alternatives; however, sibling context makes it clear.

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