boss_hr_resume

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'view', implying a read operation, but does not explain side effects, required permission context beyond roles, response behavior, or what happens when the resume is unavailable. This is minimal coverage of behavior.

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 very short and front-loaded with the main purpose, which is good. However, it contains a duplicated typo '可用性: 可用性:' and the bracketed availability block is somewhat noisy relative to the simple intent.

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 tool with no output schema and no annotations, the description gives only the core action and availability. It does not describe the returned resume content, how it relates to boss_resume_show, or any limitations, leaving an agent with incomplete context for correct selection and invocation.

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 100%, and the property descriptions already explain geek_id, job_id, security_id, and raw. The tool description adds no parameter-level meaning beyond what the schema provides, so the baseline score 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 action and resource: '查看候选人在线简历' (view candidate's online resume) in recruiter mode. It identifies a specific verb and object, but it does not distinguish itself from sibling tools like boss_resume_show or boss_resume_list.

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 provides only availability constraints (roles=recruiter, platform=zhipin-recruiter) and no guidance on when to use this tool versus alternatives. There is no mention of when-not-to-use or why it should be preferred over boss_resume_show.

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