添加求职期望
| Name | Required | Description | Default |
|---|---|---|---|
| dq | Yes | 期望地点名称 | |
| jobtitle | Yes | 职能/职位类别名称 | |
| workType | No | 学生期望工作类型。允许取值及含义：0-应届，1-实习 | |
| workweek | No | 每周工作天数 | |
| industries | No | 行业名称列表 | |
| wantSalaryLow | No | 期望薪资下限（元） | |
| otherExpectDqs | No | 感兴趣的期望地点名称列表 | |
| practiceMonths | No | 实习月数 | |
| wantSalaryHigh | No | 期望薪资上限（元） | |
| wantSalaryMonths | No | 期望薪资月数 |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are empty, so the description carries the full burden of behavioral disclosure. It only says 'add job expectation' with no details about side effects, idempotency, permissions, or return values.
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 short phrase that is under-specified rather than appropriately concise. It does not earn its place by conveying useful information beyond the name.
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?
With 10 parameters, no output schema, and no annotations, the one-line description fails to provide essential context about what a job expectation is, how fields relate, or what the tool actually does in practice.
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 input schema provides thorough descriptions for all 10 parameters (100% coverage), so the description adds no additional parameter meaning. Baseline 3 is appropriate.
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 '添加求职期望' is essentially a Chinese translation of the tool name 'add-job-want', restating it without adding specificity. It does not distinguish this tool from siblings like add-edu-exp or modify-job-want.
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?
No usage context is provided. The description does not explain when to use this tool versus alternatives such as modify-job-want, nor does it mention any prerequisites or conditions.
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.
