create-webhook-subscription

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

Beyond annotations (which indicate no readOnly, destructive, etc.), the description adds that the webhook receives POST requests on workout creation and imposes a 5-second response requirement. It does not cover failure scenarios or rate limits, but adds useful context.

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 sentences efficiently convey purpose and a key behavioral requirement. No redundant or unnecessary text.

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 simple creation tool with 2 parameters and no output schema, the description covers the main purpose and a critical constraint (timeout). It is missing potential error handling details or response format, but is adequate.

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 100%, so the description adds minimal value. It mentions the webhook receives POST requests for workouts, which relates to the 'url' parameter, but does not elaborate beyond the schema. The 'authToken' parameter is not described in the 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 'Create a new webhook subscription for this account', specifying the verb 'create' and the resource 'webhook subscription'. It also explains the webhook's purpose (receiving POST requests when workouts are created), distinguishing it from sibling tools like delete-webhook-subscription.

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 provides clear context for when to use the tool (to create a webhook subscription) and includes a critical requirement (endpoint must respond with 200 OK within 5 seconds). However, it does not explicitly mention when not to use it or provide alternatives among siblings.

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