madeonsol_first_touch_subscriptions_create

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

Annotations indicate it is a mutation (readOnlyHint=false). The description adds valuable behavioral info: returns webhook_secret only once and must be stored. No contradictions with annotations. Could mention behavior when limit exceeded or validation fails.

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?

The description is concise, front-loading the action and key constraints. The list of filters is clear but could benefit from bullet points for readability. No superfluous sentences.

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 the tool's complexity (multiple filters, no output schema), the description covers purpose, constraints, and a key behavioral trait. However, it lacks details on response structure (beyond secret) and error handling, leaving gaps for an agent.

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 75% with descriptions for name, delivery_mode, and webhook_url. The description lists filters (kol, mint_suffix, etc.) but does not explain their meanings or usage beyond names, leaving some ambiguity for nested properties.

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 tool creates a first-touch webhook subscription and lists key filters. However, it does not explicitly distinguish from sibling tools like 'madeonsol_create_webhook' or other subscription creation tools, which would elevate it to a 5.

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 specifies that it is 'ULTRA only' and has a limit of 10 active subscriptions, giving usage constraints. It does not provide guidance on when to use this over alternatives like coordination or copytrade subscriptions, lacking exclusionary context.

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