boss_ai_analyze_jd

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

No annotations are present, so the description must fully convey behavioral traits. It only states that the tool outputs a matching score and gap analysis, but does not disclose whether it is read-only, if it requires special permissions, or if it has side effects. The description is insufficient for understanding the tool's behavior beyond its output.

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 concise sentence in Chinese that efficiently conveys the tool's purpose and output. No unnecessary words or repetition.

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 there is no output schema and no annotations, the description provides a high-level overview but lacks details such as output format, limitations, or that both parameters are required. It covers the essential purpose but leaves gaps in understanding the complete behavior.

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 already describes both parameters (jd_text as job description text and resume as local resume name). The description does not add extra semantic details; it merely restates the overall purpose. With 100% schema coverage, a baseline of 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 clearly states the tool's function: analyzing a job description and evaluating resume matching, with specific outputs of matching score and gap analysis. The verb 'analyze' and resources 'JD' and 'resume' are explicit, and it distinguishes from sibling tools like boss_ai_chat_coach or boss_ai_optimize.

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 guidance is provided on when to use this tool versus alternatives such as boss_ai_optimize or boss_ai_suggest. The description lacks context about prerequisites or situations where this tool is preferred.

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