ncloud_dataflow_get_job

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

Annotations already provide readOnlyHint=true, so the description adds little beyond stating it gets information. It does not describe any behavioral traits such as response format, potential delays, or limitations. Given annotations exist, the bar is lower but the description should still add context like what fields are returned.

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 redundant words. It front-loads the verb and resource, making it easy to scan.

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 simple read-only tool with one parameter and existing annotations, the description is minimally complete. However, it does not hint at the output structure (no output schema) or confirm that the response is suitable for further operations. Could be improved with a brief note on what 'detailed information' typically includes.

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% and the schema description for jobId ('Job ID to query') is clear. The tool description does not add additional meaning beyond what the schema provides, so baseline 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 tool retrieves detailed information of a Data Flow job by ID. It differentiates from sibling tools like ncloud_dataflow_list_jobs (which lists jobs) and ncloud_dataflow_create_job (which creates). However, it could specify what 'detailed information' includes.

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 tool vs alternatives. It mentions 'by ID' implying a prerequisite (knowing the job ID), but does not explicitly state that you should first list jobs to get the ID or that this is a read-only lookup. No exclusions or alternatives mentioned.

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