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

With no annotations, the description does real work: async execution, credit consumption, and volatile in-memory job state lost on restart. However, it omits the critical follow-up behavior — that a returned job id is needed to poll via agent_job_get — and says nothing about permissions or failure modes.

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 tight clauses, front-loaded with the verb and immediately followed by the two operational caveats an agent most needs. No wasted words, though the terseness comes at the cost of the missing parameter details.

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?

Five undocumented parameters, no output schema, and no annotations mean the description should carry a heavy load, and it doesn't. An agent cannot tell what variables, target_url, or output_json_schema do, or what comes back to feed agent_job_get.

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 description coverage is 0% across 5 parameters, so the description must compensate and largely fails. 'On a task' loosely implies the required text field, but lang, variables, target_url, and output_json_schema get no mention at all.

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+resource: run the browsing agent on a task, and flags it as async. It is distinguishable from siblings like browser_navigate or pipeline_run by the 'agent job' framing, though it never explicitly contrasts with 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?

No guidance on when to use this versus pipeline_run, browser_navigate, or schedule_create. The credit-cost warning is a usage consideration but not a when-to-use rule, and there are no exclusions or prerequisites.

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