validate_function_url

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

Annotations already mark this as non-read-only and destructive, and the description adds the concrete side effect: completing the sync step. It also explains idempotent completion behavior, that Staticbot continues checking on error, and that the agent should re-fetch get_migration afterward. No contradiction with annotations.

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 dense but every sentence carries a necessary decision rule: when to use, where to find parameters, what completed means, what not to call, and how to handle errors. It is front-loaded with the core action and avoids filler.

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 stateful tool in a migration workflow, the description covers input sourcing, side effects, return value semantics, error handling, and next-step routing. The presence of an output schema plus this rich behavioral context leaves no meaningful gap for the agent.

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 baseline is 3. The description adds real value beyond the schema by explaining how to obtain functionUrl from the job's inputData and how to derive it from sourceProjectRef and functionName. jobId semantics are consistent with the schema's MANUAL_SYNC_LOVABLE / MANUAL_SYNC_BASE44 guidance.

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 opens with a specific verb and resource: check that the Staticbot export edge function is reachable, and complete its sync step when it is. It clearly differentiates itself from the sibling complete_migration_job by explicitly telling the agent not to call that tool afterwards.

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?

It states precisely when to use the tool: after the user pasted the deploy command into Lovable AI chat. It also gives the exact source for function_url, explains how to derive it, and gives error-path guidance to poll get_migration instead of calling other completion tools. This is exemplary usage guidance.

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