gcloud_dataflow_jobs_describe

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 it retrieves information, but does not mention read-only nature, potential side effects, authentication requirements, or rate limits. This is insufficient for a tool with no 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 a single, concise sentence with no extraneous words. However, it is overly minimal and lacks structure (e.g., front-loading critical info). Not every word earns its place, as it fails to add value beyond the name.

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 has 2 parameters, no annotations, and no output schema, the description should be more comprehensive. It does not explain what kind of information is returned (e.g., job status, metrics), permission needs, or common errors. It is incomplete for effective use.

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 100%, so the baseline is 3. However, the description adds no value beyond the schema: it does not explain what 'job_id' is or how to obtain it, nor does it provide context for 'region' (e.g., default value impact, format). The description contributes nothing to parameter understanding.

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') and the resource ('detailed information about a Dataflow job'). It distinguishes the tool from siblings like 'gcloud_dataflow_jobs_list' (which lists jobs) and 'gcloud_dataflow_jobs_cancel' (which cancels a job). However, it does not explicitly mention that it targets a single job by ID, which would add clarity.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., need a job ID), when to prefer this over listing jobs, or scenarios where describing is not appropriate. No explicit context or exclusions are given.

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