Create Webhook Subscription

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

Beyond the annotation readOnlyHint=false, the description discloses a critical behavior: the returned secretKey is shown only once and must be surfaced to the user immediately. This is essential context for handling the tool's output and is not present in annotations or schema. No contradictions with 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?

The description is two sentences, front-loaded with the primary purpose and followed by the critical secretKey detail. Every sentence earns its place with no redundant or fluff content.

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 create tool with no output schema, the description sufficiently covers the action, the one-time secretKey return, and the verification header. It does not explain error cases or prerequisites, but the schema provides parameter constraints (e.g., HTTPS URL). This is adequately complete given the tool's simplicity.

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 description coverage is 100%, so the parameters (name, targetUrl, eventTypes) are already well-documented in the schema. The description adds no additional parameter-level meaning beyond what the schema provides, matching the baseline for high schema coverage.

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's function: 'Subscribe an endpoint to Hyros events.' This is a specific verb+resource combination that distinguishes it from sibling tools like hyros_get_webhook_subscriptions (list) and hyros_delete_webhook_subscription (delete). The mention of returning a secretKey for verification further clarifies its purpose.

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 implies usage by saying 'Subscribe an endpoint to Hyros events,' but it does not explicitly state when to use this tool versus alternatives (e.g., when to list or delete subscriptions). No alternatives or exclusions are mentioned, so guidance is only implicit.

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