hires_advance_applicationAdvance an application to the next stage in workflow order; no stage_id needed.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| include | No | Embed: candidate, cv.text, job. Pass candidate,job so the widget can link to the candidate and job pages |
Changes observed during successful MCP inspections.
Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / id / descriptionRemoved value: -"Application ID."Input schema / properties / include / descriptionPrevious value: -"Comma-separated relations to embed: candidate, cv.text, job. Set to `candidate,job` so the widget can link the candidate name to their profile and the job title to its pipeline view."New value: +"Embed: candidate, cv.text, job. Pass candidate,job so the widget can link to the candidate and job pages"Input schema / properties / include / descriptionPrevious value: -"Comma-separated relations to embed: candidate, cv.text."New value: +"Comma-separated relations to embed: candidate, cv.text, job. Set to `candidate,job` so the widget can link the candidate name to their profile and the job title to its pipeline view."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and openWorldHint=true, covering the mutating nature. The description adds that the stage is determined by workflow order and that stage_id is unnecessary, providing behavioral context beyond the annotations, though it omits side effects like notifications.
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 sentence with the action verb front-loaded and the critical detail (no stage_id) included without extra words. Every word earns its place.
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 two-parameter mutation tool with annotations covering safety, the description is adequate for the core operation. However, it doesn't mention return values, side effects, or how to choose this over related tools, leaving some gaps for a fully informed call.
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 only 50% (include is described, id is not). The tool description does not mention either parameter, failing to compensate. An agent must rely on the schema for include's meaning and has no guidance for id beyond it being required.
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 the verb 'Advance' and resource 'application', plus specific behavior 'to the next stage in workflow order' and clarifies no stage_id is needed. This clearly distinguishes it from sibling tools like move_application and transfer_application without needing to inspect their schemas.
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 description gives a precise action and the key constraint that stage_id is not required, which is useful. However, it does not explicitly say when to use this tool versus alternatives such as move_application or transfer_application, leaving the decision to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.