conduyt_create_call_flow_function

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

With no annotations, the description carries the full burden and delivers: it discloses the HMAC signing scheme, the idempotency key format, that the secret is write-only, and hard constraints (https/public hosts only, no redirects, 2-8s timeout, 64 KB cap). This is exactly the behavioral context an agent needs to configure a valid endpoint.

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?

Purpose is front-loaded in the first clause and every subsequent detail (signature format, constraints, write-only secret) is load-bearing. The signing header details are packed tightly into one long parenthetical, which is dense but not wasteful.

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?

Despite having no output schema and no annotations, the description fully specifies the request/response contract (snapshot POSTed, expected 200 JSON mapping into call attributes), so an agent can call it and understand downstream behavior without further sources.

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 already 100%, so baseline is 3; the description adds meaning beyond the schema by explaining that 'secret' is write-only and is the HMAC key against which the endpoint verifies X-Conduyt-Signature. That extra semantic linkage lifts it to a 4.

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?

States a specific verb and resource ('Register a call-flow function endpoint') and flags the admin requirement. The verb 'register' cleanly separates it from the sibling update/delete/test/list call-flow-function tools without needing to name them.

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 '(admin)' tag gives a clear permission precondition, and the detailed protocol requirements tell the agent exactly what the target endpoint must satisfy. It stops short of naming an alternative (e.g. update_call_flow_function) or stating when not to use it, which keeps it below a 5.

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