scf_get_webhook

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

No annotations are provided. The description indicates a read operation (get) which is generally safe and non-destructive. It discloses the types of details returned (delivery stats, allowed evidence IDs, rate-limit configuration) but does not mention any side effects, required permissions, or rate limits.

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 14-word sentence that is direct and free of unnecessary words. Every part adds value.

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?

Given no output schema, the description sufficiently indicates the return content (delivery stats, allowed evidence IDs, rate-limit configuration). Parameter descriptions include guidance on obtaining IDs. A hint about the output structure or expected response size would improve completeness, but current level is adequate.

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?

Both parameters have descriptions in the schema that add context beyond name and type: org_id includes 'Organization UUID — obtain from scf_list_organizations' and endpoint_id includes 'Webhook endpoint UUID — obtain from scf_list_webhooks', providing clear guidance on how to obtain valid values. Schema coverage is 100%.

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 action 'Get' and the resource 'one webhook endpoint's detail', and specifies what details are returned: 'delivery stats, allowed evidence IDs, and rate-limit configuration'. This distinguishes it from sibling tools like scf_list_webhooks (list all) and scf_create_webhook (create).

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 does not explicitly state when to use this tool versus alternatives or provide prerequisites. The context implies it is for retrieving a single webhook by ID, but no guidance on when not to use or which sibling tool to use instead is given.

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