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

With no annotations, the description carries the full behavioral burden and does so thoroughly: it flags create as returning the full URL with token exactly once and non-retrievable later, notes list/get omit the URL token, and states delete stops accepting POSTs immediately. It also discloses the signing secret header behavior. No contradictions with annotations exist.

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 longer than average but earned: it front-loads the resource definition, then organizes each mode into a scannable bullet, and the mappingJson example is dense but directly useful for the most complex parameter. There is no filler or tautological repetition.

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 nine-parameter router tool with no annotations and no output schema, the description covers all actions, required versus optional parameters, destructive behavior, and the one-time token retrieval caveat. Nothing an agent needs to invoke the tool safely and correctly is missing.

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 baseline is 3. The description adds value beyond the schema by explaining the native-vs-mapped default decision, clarifying that signingSecret is optional and associated with X-Groundbase-Signature, and instructing that update should only include fields to change. It is not a 5 because several parameter behaviors (e.g., ipAllowlist empty meaning) are left to the already-sufficient schema rather than enriched.

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 definition names the resource ('inbound webhooks'), explains what they are ('URLs the world POSTs to so Groundbase creates contacts/deals/tasks/etc.'), and enumerates five concrete operations dispatched by `action`. This clearly differentiates the tool from the sibling outbound_webhooks_manage without needing to open the schema.

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?

Each action has an explicit when-to-use rule and prerequisites: list needs no args, get/update/delete require `id`, create requires `name`, and delete explicitly requires user confirmation. It also gives the mappingMode decision rule ('use mapped only when the sender has a fixed payload shape that needs translating'). This is strong enough to select the right operation and avoid mistakes.

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