Get Outbound Webhook Logs

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds context about 'delivery logs' and 'monitor and debug', but does not disclose additional behavioral traits like log ordering, retention, or rate limits. With annotations present, the description adds limited value beyond them.

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 sentence of 13 words that front-loads the purpose and usage. Every word is necessary; no padding or redundancy.

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 retrieval tool with three well-documented parameters, the description is reasonably complete. It could mention the expected return structure (since no output schema exists) or pagination defaults, but the schema and context signals provide that information. Overall sufficient.

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% with clear descriptions for all three parameters (id, page, limit). The description does not add any additional meaning beyond what is already in the schema, so it meets the baseline but does not exceed it.

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 it retrieves delivery logs for an outbound webhook, using specific verb+resource. It implicitly distinguishes from the sibling 'neuron_get_webhook_logs' by specifying 'outbound', which disambiguates the tool's scope.

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 says 'to monitor and debug event delivery', providing clear when-to-use guidance. However, it does not explicitly state when not to use this tool or mention alternatives (e.g., for inbound webhooks, use neuron_get_webhook_logs).

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