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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-dependency profile is covered by structured data. The description adds only 'full detail,' which implies a richer payload than the board endpoint but says nothing about auth, rate limits, or failure modes for a bad tenant/site/path.

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?

One short, front-loaded phrase with zero filler, and the distinguishing word 'Single' comes first. It is terse rather than padded, though it verges on under-specification.

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?

An output schema exists, so return values need not be described, but with four undocumented required parameters and no usage context, the definition is not complete enough for an agent to call this correctly without trial and error.

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?

Four required parameters (tenant, datacenter, site, path) have 0% schema description coverage and the description mentions none of them. An agent has no way to know what values are valid for 'site' or 'path' or where to obtain them, so the description fails to compensate for the schema gap.

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 phrase 'Single Workday job with full detail' names the resource (a Workday job), its cardinality (single), and its depth (full detail), which cleanly separates it from the sibling jobs_workday_board that returns listings. The retrieval verb is only implied, but an agent can still tell what it gets back.

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?

There is no statement of when to use this tool versus jobs_workday_board or the other jobs_*_job siblings, and no hint that the four required identifiers typically come from a board/listing call. The agent must infer the workflow entirely.

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