boss_preset_list

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

There are no annotations, so the description carries the burden of explaining behavior. '列出' implies a read-only list operation, but the description does not explicitly state that it has no side effects, what the returned data will contain, or whether any authentication/availability restrictions apply beyond the provided roles/platforms note.

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 appropriately short and front-loads the core action. It loses a point because of the duplicated '可用性: 可用性:' typo and the trailing 'recruiter_platforms=-' artifact, which adds minor noise.

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 zero-parameter list tool, the description covers the basic operation and availability, but it omits what the output will look like and does not clarify when this should be used over sibling tools. It is minimally adequate but not complete.

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 input schema is empty with zero parameters, so there are no parameter semantics to explain. The baseline for a zero-parameter tool is 4, and the description does not need to add parameter-level detail.

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 clearly states a specific verb ('列出' / list) and resource ('所有搜索预设' / all search presets), so an agent can understand the core operation. It does not explicitly compare itself to sibling tools such as boss_preset_add or boss_preset_remove, but the list-vs-mutate operation is reasonably evident.

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?

No guidance is given on when to use this tool versus alternatives like boss_config, boss_search, or the preset add/remove tools. The only context provided is an availability string for roles and platforms, which is operational metadata rather than usage guidance.

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