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

Annotations already declare readOnly=false, destructive=false, idempotent=true, and openWorld=true, covering the safety profile. The description adds no behavioral detail beyond them, notably omitting whether this is a partial merge or full replace of unspecified fields, which is the key open question for an update tool.

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?

A single, front-loaded sentence with no filler. The verb and target resource lead, and the field list is compact.

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?

Adequate for a moderately complex mutation with full schema coverage and annotations, but it leaves partial-update semantics and sibling routing (update_webhook vs update_outbound_webhook) unaddressed, both of which an agent would want resolved.

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 every parameter is already documented in the schema and the baseline is 3. The description names url, eventTypes, and filterPrompt but omits id and name and adds no syntax or format meaning beyond the schema.

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?

States a specific verb ('Modify') and resource ('existing outbound webhook's configuration') and enumerates the modifiable surface (URL, event types, filter prompt). The 'outbound' qualifier helps distinguish it from the sibling neuron_update_webhook, though it never explicitly contrasts the two.

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?

No guidance on when to use this versus neuron_create_outbound_webhook, neuron_delete_outbound_webhook, or neuron_update_webhook. It describes the action but gives no context, prerequisites, or exclusions to steer selection.

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