tracecat_get_webhook

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

No annotations are provided, so the description must disclose behavioral traits. It only states the tool gets webhook details and lists some attributes, but does not mention whether the operation is read-only, idempotent, requires authentication, or any error conditions. This is insufficient for a mutation-free operation.

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 with 9 words, front-loading the verb and resource. Every word is necessary to convey the core purpose. No redundant information.

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 the tool's simplicity (one required parameter, no output schema), the description covers the essential purpose and key return fields (URL, status, methods). It is sufficient for an agent to understand what the tool does, though additional details on error handling could enhance completeness.

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%, so the schema already documents the only parameter (workflow_id). The description does not add additional meaning or usage hints for the parameter beyond the schema. Baseline score of 3 is appropriate.

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 verb 'Get', the resource 'webhook details', and scope 'for a workflow', and lists specific fields (URL, status, methods). This distinguishes it from siblings like tracecat_get_workflow or tracecat_list_workflows.

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 implies usage for retrieving webhook configuration, but does not explicitly state when to use vs alternatives or provide context on prerequisites. The purpose is clear enough to infer usage, but no alternative tools or exclusions are mentioned.

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