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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds essentially nothing behavioral beyond that, but it does echo the tenant-scoping context, which is minor. It says nothing about pagination behavior implied by limit/offset, rate limits, or result shape.

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 short sentence with no wasted words, front-loading the resource and its tenant scope. Its problem is under-specification, not verbosity, so it is well-sized for what little it attempts.

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?

Although an output schema exists (so return values needn't be described), this is a 6-param tool with three required, non-obvious parameters at 0% schema coverage. A one-sentence description with no usage guidance or parameter meaning is far short of complete.

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 0%, so the description must compensate for six undocumented parameters; it only mentions 'tenant'. The non-obvious Workday-specific params (datacenter, site) and the search/limit/offset controls are left entirely unexplained in both schema and description.

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 names the resource (a Workday job board) and scopes it to a tenant, so an agent knows it targets a board-level listing rather than a single job. However, it has no verb ('list/fetch') and never distinguishes itself from the sibling jobs_workday_job, leaving the board-vs-job boundary to inference. Purpose is conveyed but vague.

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 when-to-use guidance, no prerequisites, and no reference to the alternative jobs_workday_job or any other board tool. The agent gets no signal about when this board endpoint is the right choice over the single-job sibling.

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