boss_ai_resume_optimize

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two meaningful traits: the operation is suggestion-only and does not modify the resume, and it is gated to candidate role on the zhipin platform. It says nothing about output format, how the resume content is obtained, or any cost/rate limits.

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 compact sentence plus an availability tag, with the core purpose front-loaded. Nothing is wasted, though the bracketed availability metadata is somewhat cryptic in placement.

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 3-parameter advisory AI tool with no output schema and no annotations, the description covers intent and the non-mutating nature but leaves return-value expectations and resume-source behavior unstated. It is minimally sufficient but not thorough.

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 coverage is 100%, so job_id, jd_text, and their mutual exclusivity are already documented in the schema. The description adds no semantics about parameters beyond what the structured fields already state, so the baseline of 3 applies.

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 names a specific verb and resource: it optimizes resume wording based on the target position, and it clarifies the operation is advisory only ('仅建议，不修改简历'). It does not, however, explicitly distinguish itself from similarly named siblings such as boss_ai_optimize or boss_ai_suggest, so an agent must infer the difference from the scope note.

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?

There is no explicit when-to-use/when-not-to-use guidance or mention of alternatives. The embedded availability constraint (roles=candidate; candidate_platforms=zhipin; recruiter_platforms=-) does imply who may call it, which is useful, but eligibility is not the same as usage guidance.

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