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

No annotations are provided, so the description carries the full burden. It discloses the returned fields (templateId / 名称 / 说明 / canOpen / missingHandlers / 动作清单) and a critical behavioral rule: canOpen=false means not openable and must not be recommended. That is exactly the kind of constraint an agent needs. It stops short of permission or rate-limit notes, but for a no-param read tool this is strong.

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?

Front-loads purpose, then usage, then return shape, then exclusion, then the canOpen caveat, ending with 参数：无. Every sentence carries information. It is slightly dense but no sentence is wasted.

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 zero-param list tool with no output schema and no annotations, the description covers what it returns, when to use it, when not to, and the canOpen constraint. That is sufficient for correct invocation. Minor gap: no mention of ordering or pagination, but none is implied.

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?

Parameter count is 0, so the baseline is 4. The description correctly notes 参数：无, which is accurate and leaves no ambiguity.

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 explicitly distinguishes from the sibling list_my_staff by naming it. An agent can route between the two without opening either schema.

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?

Explicit when-to-use ('想知道系统能开哪些岗位'、用户要开通新岗位时) and when-not ('别用它找已开好的岗位'——那是 list_my_staff). The exclusions and alternative are named directly.

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