boss_greet

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

No annotations are provided, so the description carries the full burden. Greeting is a mutating, outreach action with side effects, yet the description never states whether it sends a message, is rate-limited, or is irreversible. The availability constraint is the only behavioral context given.

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?

Two short sentences that are front-loaded with the core action. It is slightly marred by the duplicated '[可用性: 可用性:' text, indicating a formatting glitch.

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 simple two-required-param action with no output schema, the essentials are covered. However, with no annotations and no disclosure of side effects, success/failure behavior, or limits of a write-like outreach, it falls short of complete for an agent to invoke confidently.

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%, so both parameters (job_id, security_id) are fully documented in the schema. The description merely restates '需要 security_id 和 job_id', adding no meaning beyond the structured field definitions.

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?

States a specific verb and target: '向招聘者打招呼' (greet the recruiter). An agent understands the action, but the description never distinguishes it from the closely related boss_batch_greet or explains the single-vs-batch scope.

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 availability clause (roles=candidate, candidate_platforms=zhipin) implies a calling context, but there is no explicit when-to-use guidance and no reference to alternatives like boss_batch_greet for bulk greeting.

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