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

The annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by enumerating the actual status label values and setting the scope as job status labels, which goes beyond the annotation title's generic 'List application statuses'.

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 front-loaded sentence states the operation, the resource, and the concrete label values with zero filler or repetition. Every word contributes to the agent's understanding.

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, parameterless, read-only enumeration tool with no output schema, the description is fully sufficient. It tells the agent exactly what is returned: job status labels with their known values. The annotations cover side effects, so nothing essential 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?

The tool has zero parameters and schema description coverage is 100%, so the schema is trivially complete. The description's enumerated status values provide a little extra contextual meaning, but with no parameters there is little semantic work for the description to do, matching the baseline for a no-parameter tool.

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 a specific verb and resource: 'List job status labels' and enumerates the exact statuses: draft, published, on_hold, closed, archived. This is immediately distinguishable from the many sibling list_* tools because it specifies precisely what is being listed and the value domain.

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 explicit guidance about when this tool should be used versus alternatives. With over 130 sibling tools, including several list_* tools like hires_list_jobs, hires_list_workflow_stages, and hires_list_rejection_reasons, the description offers no exclusions or decision criteria, so the agent must infer applicability from the name alone.

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