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

No annotations, so the description handles the behavioral load. '列出' clearly signals a read-only list, it enumerates the exact return fields, and it establishes the tool as the authoritative source for slugs (warning against hallucination), which is a meaningful behavioral contract for an agent. It doesn't cover auth or pagination, but for a zero-parameter list tool that is a minor gap.

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?

Three short, front-loaded clauses: purpose and return fields first, usage/routing second, parameters last. No wasted words; the only redundancy is '参数：无', which is harmless.

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 with no annotations and no output schema, the description is nearly complete: it states purpose, usage, the authoritative slug contract, and the fields returned. The only missing element is return shape/pagination detail, which is minor for this tool.

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?

With zero parameters and schema coverage 100%, the baseline is 4. The description redundantly states '参数：无', matching the empty schema, and adds no parameter meaning because none exists.

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 ('我名下的数字员工岗位') and enumerates the returned fields (slug / 名称 / 模板 / 画布链接). It also differentiates itself as the authoritative slug source for all sibling position tools, so an agent can tell why to call it rather than get_job or list_templates.

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?

Explicitly says to use it when the user asks '我有哪些岗位' and mandates that all subsequent position-operation tools must obtain slugs from this call rather than memory. This gives both the trigger condition and a strong routing prerequisite, leaving little to inference.

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