madeonsol_first_touch_subscriptions_create

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

Explicitly states 'Returns webhook_secret ONCE — store it', a critical one-time behavior. Annotations (readOnlyHint=false) are consistent but the description adds essential behavioral detail beyond the structured 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?

Three concise sentences: purpose, constraints/filters, return value. Front-loaded and efficient with no unnecessary 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?

For a creation tool with no output schema, the description covers parameters, constraints, and the secret's one-time nature. Could mention error implications but sufficient for correct invocation.

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% but the description enumerates all filter parameters, compensating for missing schema descriptions. It adds practical meaning beyond the structured input.

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 'Create a first-touch webhook subscription' and lists specific filters. It distinguishes from sibling tools like delete, get, list, and 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?

States 'ULTRA only — up to 10 active', providing clear constraints and context for when to use. Although it doesn't explicitly list alternatives, the limitation is well communicated.

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