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

With no annotations at all, the description carries the full disclosure burden and does deliver some of it: payloads are signed, auth is stored and never shown again, and the token is a secret that should never be posted. It doesn't disclose delivery failure behavior, retry/rate-limit characteristics, what the read mode actually returns, or what each output format changes about the payload shape.

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?

Purpose is front-loaded in the first clause and every subsequent clause carries an actionable mode or format detail. The format list and auth rule make it dense but not padded; a slight cost is that mode-selection, format list, and auth semantics are run together in one block rather than separated.

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 mutation-style configuration tool with six parameters, zero annotations, and no output schema, the description should say more about the read mode's return and about failure/verification behavior ('test' implies verification but the result isn't described). Combined with the thin behavioral transparency, an agent still lacks enough to predict outcomes beyond the happy path.

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 83%, so the schema already documents most parameters and the baseline applies. The description does add real meaning the enum can't convey by glossing each format value (github = repository_dispatch, claude = Claude Code routine API trigger) and by explaining that auth becomes the Authorization header with Bearer auto-prefixed when no scheme is given. That lifts it modestly above baseline.

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 opens with a concrete outcome: Wezzet POSTs to your https URL when you get a DM, immediately establishing this is a webhook-configuration tool rather than a messaging tool. It doesn't name any sibling or explicitly distinguish itself from dm/inbox, but no sibling covers webhook setup, so the purpose is unambiguous.

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?

It gives explicit per-mode routing: 'Call with url to set it, off to remove, test to send a test ping, or nothing to see the current setting,' which tells the agent exactly which argument combination produces which behavior, including the no-argument read case. It stops short of stating prerequisites (e.g. needing a token) or exclusions, so it's clear context without full when/when-not coverage.

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