yupao_save_preset

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation and safety profile are partly covered. The description adds that unverified platform filters run locally ('平台未核实的过滤在本机执行'), which is useful behavioral context, but it does not explain persistence, overwrite behavior, or whether an existing preset name is replaced.

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 definition is compact and front-loaded, with purpose stated first and parameter semantics following. It is efficient, though the terse phrasing leaves important behavior implicit.

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 mutation tool with 10 parameters and no output schema, the description is incomplete. It omits key details such as whether the preset requires a unique name, whether saving overwrites an existing preset, what is returned, and session requirements.

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% with 10 parameters, so the description must carry the burden. It clarifies salary units ('元/月') and that education/experience refer to the person's own conditions, but leaves name, keywords, excluded_terms, required_terms, page_size, and city semantics undocumented.

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 and resource: '保存搜索条件' (save search criteria). It is distinguishable from siblings like yupao_search_preset, yupao_list_presets, and yupao_remove_preset, though it does not explicitly name or contrast them.

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?

There is no guidance on when to use this tool versus alternatives such as yupao_search_jobs or yupao_search_preset. It also does not state prerequisites, exclusions, or typical scenarios for saving a preset.

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