List Webhooks

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

The annotation includes 'openWorldHint: true', which already informs that the list may not be exhaustive. The description adds no further behavioral context (e.g., pagination, rate limits). It does not contradict the annotation, but also does not enhance it.

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 a single, concise sentence that gets straight to the point. No unnecessary words or redundancy. It is effectively front-loaded.

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 listing tool with one parameter and no output schema, the description is sufficiently complete. Combined with the annotation, it provides all necessary context for use.

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?

There is only one parameter ('botId'), and the input schema provides a clear description. The tool description adds no additional semantic meaning beyond the schema, which is adequate given 100% 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 purpose: 'List all inbound webhooks configured for a specific bot'. It specifies the resource (inbound webhooks) and the context (for a specific bot). Although it does not explicitly differentiate from siblings like 'neuron_list_outbound_webhooks', the use of 'inbound' provides sufficient distinction.

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 lacks any guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions. Given many sibling list tools exist, usage guidance is minimal.

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