boss_agent_pending

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

No annotations are provided, so the description must carry the full behavioral burden. 'View' (查看) implies a read-only listing, and the availability bracket usefully discloses role and platform gating, but the description says nothing about whether the pending items can be acted on, whether reads are safe, or what the queue contains.

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?

It is a single front-loaded sentence that puts the purpose before the bracketed metadata, with no filler. The bracketed availability block is dense but carries real information rather than padding.

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 zero-parameter read tool with no output schema, the definition covers what the tool is but not what it returns: what a 'pending action' looks like, whether the list is empty in common cases, or what an agent should do with the result. Adequate but with clear gaps.

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 tool takes zero parameters, so the baseline is 4; the description correctly implies no input is needed to fetch the queue. Nothing is missing on the parameter side.

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: viewing the pending-action queue left over from older versions ('查看旧版本遗留的待执行动作队列'). The 'legacy compatibility interface' framing distinguishes it from active agent tools such as boss_agent_run, boss_agent_review, and boss_agent_stats, though it never names those siblings 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?

Usage is only implied: 'compatibility interface' and 'left over from older versions' suggest it is for legacy workflow state, not for normal operation. The bracketed availability metadata (roles=candidate, recruiter; platforms=zhipin) gives a real precondition, but there is no explicit when-to-use versus when-not-to-use or a named alternative.

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