boss_favorites_list

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

With no annotations, the description still discloses the key behavior '不落库' (does not persist to the database), which tells the agent this is a side-effect-free read. It also indicates that '有效状态' (validity status) is included in the result. It stops short of describing pagination behavior, total page counts, or what happens at out-of-range pages.

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?

One compact sentence with the core purpose front-loaded, followed by a bracketed constraint tag. Nothing is redundant, though the dense bracket notation is less scannable than prose.

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 low-complexity read tool with one optional parameter and no output schema, the description covers purpose, non-persistence, returned status, and platform eligibility. Only the paging mechanics are under-specified, which is a minor gap.

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?

There is a single optional integer parameter 'page' with 100% schema description coverage, so the schema already carries the semantics. The description's phrase '单页' reinforces that results are paged but adds no default value, range, or 1-based/0-based convention beyond what the schema states.

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 ('预览'/preview) and a specific resource ('BOSS 职位收藏' job favorites list) plus what is returned ('单页及有效状态'). It is clearly distinguishable from siblings such as boss_shortlist_list or boss_watch_list by the 'favorites' domain, though it never names those alternatives 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?

The bracketed availability block ('roles=candidate; candidate_platforms=zhipin; recruiter_platforms=-') does give a precondition for when this tool is callable, which is useful gating. However, there is no guidance on when to use this versus the other list-style siblings, and no note on how to page through results.

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