boss_detail

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

No annotations provided, and description only states purpose. Does not disclose side effects, auth needs, rate limits, or behavior on invalid input.

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?

Short and front-loaded. One sentence plus a usage note. Efficient but could include more behavioral detail without becoming verbose.

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?

Adequate for a simple detail view, but lacks information about response format or constraints. With no output schema and no annotations, more completeness would help.

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?

Adds context that security_id is from search/recommend and job_id enables fast track, exceeding schema descriptions. Schema coverage is 100%.

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?

Clearly states the action (查看/view) and resource (职位详情/job details), and specifies the parameter source. However, it doesn't differentiate from sibling tools like boss_hr_jobs_detail or boss_show explicitly.

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?

Implies usage context by noting security_id comes from search/recommend, but does not mention when not to use or alternatives.

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