hcloud_show_drs_job

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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety and idempotency profile is covered without the description's help. The sentence adds nothing beyond them - no indication of what detail fields come back, whether a missing job returns an error or empty result, or any auth/region scoping caveat - so it is minimum viable, not rich.

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?

A single six-word sentence, front-loaded with the verb and carrying no filler or redundancy. It is lean, though its brevity comes partly from omitting anything useful rather than from tight editing.

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 trivially simple two-required-parameter read tool with full schema coverage and safety annotations, the definition is adequate to invoke correctly. With no output schema, however, an agent has no idea what 'details' comprises, and that gap is left entirely unaddressed.

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% with both required parameters (job_id, region) documented in the schema. The description only restates 'a specific DRS job', adding no format hints for job_id or semantic explanation of region scoping, so the baseline 3 applies.

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 states a specific verb ('Get details of') and resource ('a specific DRS job'), and the word 'specific' distinguishes single-item retrieval from the sibling hcloud_list_drs_jobs. It does not name that sibling explicitly, which keeps it short of a 5.

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?

Usage is only implied: 'specific DRS job' signals this is the detail lookup that follows a listing, and the required job_id reinforces it, but there is no explicit statement of when to use this versus hcloud_list_drs_jobs or hcloud_list_drs_quotas, and no prerequisites or error-case guidance.

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