yupao_search_preset

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's job is to add operational context, which it does: it discloses that each page yields at most 10 full JD reads and that unmatched criteria are surfaced separately as items to verify. That volume pacing and the 'unknown conditions' handling are real behavioral traits not present in the annotations.

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 tight clauses separated by a semicolon, with the core action front-loaded and no filler. Density comes at some cost to parseability for non-Chinese readers, but every clause carries information.

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?

With no output schema, the description should say more about what comes back (a result list plus a separate unresolved-criteria bucket is only hinted at via '单列待核实'). It also omits prerequisites such as session validity or what happens if the named preset does not exist, which matters given the sibling yupao_check_session and yupao_list_presets tools.

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 0%, so the description bears the burden. It implies `name` is a preset identifier ('按预设') and that `page` controls paging with '每页最多 10 个详情', but it never explicitly defines either parameter, give the page-size constant in relation to the param, or state whether page is 1-indexed.

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 resource ('按预设搜索' = search by preset) plus concrete follow-on behavior (reads full JD, local filtering). An agent can tell this is a preset-driven search rather than a raw keyword search, though the distinction from the sibling yupao_search_jobs is never made explicit.

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 phrase '按预设' implies the precondition that a preset must exist (matching the required `name` param), and '读取完整 JD 后本机筛选' implies this is the heavyweight search to use when local filtering of full postings is wanted. But there is no explicit when-to-use, no exclusions, and no pointer to yupao_search_jobs or yupao_list_presets as alternatives.

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