scf_create_webhook

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

Discloses admin role requirement and the irreversible retrieval of the secret (write operation). Without annotations, the description carries the full burden and covers key behavioral traits, though could mention idempotency or side effects if any.

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?

Two sentences, fully front-loaded with purpose, then essential behavioral warning. No wasted words.

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?

Covers main action, critical return value warning, and role requirement. Lacks output format or error behavior, but given no output schema and 5 parameters, it is sufficiently complete for agent invocation.

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%; the schema already provides detailed descriptions for each parameter. The main description adds no additional semantics for parameters beyond the secret return behavior.

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?

Clearly states the action 'Create', the resource 'webhook endpoint', and the context 'for evidence-inbox ingestion (write — admin role)'. Distinct from sibling tools like list, get, delete, rotate.

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?

Provides critical 'store it immediately; it cannot be retrieved later' guidance for the HMAC secret. However, does not explicitly state when to use this tool vs alternatives, though sibling tools are mostly different operations.

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