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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds useful context by clarifying that the path "is not a public job URL" and that the other three values should be reused from the board, guarding against the common mistake of pasting a job URL. It does not discuss rate limits or failure modes, so it stops short of a 5.

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 sentences, zero waste. The primary action leads, and the parameter-sourcing constraint follows immediately. Every clause contributes actionable information.

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 explained, and the description covers what an agent needs: the action, the four inputs, and where to source them. Nothing required for a correct call is missing.

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 already 100%, so the baseline is 3; the description earns above that by clarifying provenance (externalPath comes from the board, and tenant/datacenter/site must be reused from that same board). It clarifies how the parameters relate, but does not add format or syntax detail beyond the schema.

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 and resource ("Fetch one Workday job record") and enumerates the payload fields returned (full description, location, requisition ID). It also names the sibling jobs_workday_board, so an agent can distinguish this detail fetch from the board listing without opening a schema.

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?

Explicitly instructs the agent to take `externalPath` from jobs_workday_board and reuse that board's `tenant`, `datacenter`, and `site`. This is a clear prerequisite chain that routes the agent to the correct sibling before invoking this tool, leaving no inference needed.

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