hires_list_experience_levels

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

No annotations are provided, so the description carries full disclosure burden. It only states the action and resource without mentioning read-only behavior, return format, pagination, or permissions. The verb 'list' implies a read operation, but the description does not explicitly disclose any behavioral traits.

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?

The description is a single, 9-word sentence that front-loads the action and resource. It contains no filler words and earns its place by also adding the use-case context.

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?

Given the tool's simplicity (no parameters) and no output schema, the description explains the tool's purpose but does not describe the shape of the return value (e.g., whether it returns IDs, labels, objects). This is a gap for full completeness, though invocation is straightforward.

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, so the input schema is trivially fully covered. The rule states that with 0 params, the baseline is 4; the description does not need to add parameter details and does not detract from 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?

The description uses the specific verb 'List' and identifies the resource as 'experience level taxonomy values', which clearly differentiates it from sibling tools like list_education_levels or list_employment_types. The added phrase 'role seniority modeling' provides further contextual purpose.

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?

The phrase 'for role seniority modeling' gives clear application context, implying when this taxonomy list would be needed. However, it does not explicitly mention alternatives or when not to use it, so it lacks explicit exclusions but still offers clear context.

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