madeonsol_create_webhook

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

Annotations already indicate mutation (readOnlyHint=false) and non-idempotence (idempotentHint=false). The description adds the subscription requirement but fails to disclose risk of duplicate webhooks, side effects, or required authentication beyond subscription. Minimal value added over annotations.

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 concise sentences: first explains purpose and benefit, second adds a critical prerequisite. No redundant or filler content. Front-loaded with the core action.

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?

The description is functional but lacks return value details (no output schema). It doesn't mention management via related tools (list, delete, test). Given the tool's complexity and sibling context, it could provide more guidance on expected behavior after creation.

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?

Input schema provides 100% parameter descriptions, and the tool description does not add extra meaning beyond the schema. Since schema coverage is high, a baseline of 3 is appropriate. No parameter-level enrichment in description.

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 the action ('Register a webhook URL') and the specific purpose ('receive real-time push notifications for KOL trades and deployer alerts'). It distinguishes from sibling webhook tools (delete, list, test) by being the creation operation, and from other alert creation tools by its subscription scope.

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 mentions the subscription prerequisite but does not explicitly guide when to use this tool versus siblings like 'madeonsol_coordination_alerts_create' or 'madeonsol_deployer_alerts'. No when-not or alternative references, leaving the agent to infer from event type options.

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