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

No annotations are provided, so the description carries the full behavioral burden. It discloses one important trait — '需 API Key' (requires an API key) — and implies a read-only fetch via '取', but says nothing about rate limits, error behavior, or output shape beyond the field list.

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 tightly scoped sentences; the operation and its returned contents come first, the parameter provenance second, and the auth note third. No filler.

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 one-parameter getter with no output schema and no annotations, the description covers the essentials: what is fetched, what fields come back (compensating for the absent output schema), where the id originates, and the auth requirement. Only behavioral edge cases (errors, limits) are left unaddressed.

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 must compensate, and it does: it explains that job_id is the integer id returned as items[].job_id from tpool_search_jobs. That provenance meaningfully exceeds the bare 'Job Id' property name in the schema.

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+resource — '取单个岗位详情' (fetch a single job's details) — and enumerates the returned fields (JD body, education/experience/skill requirements, salary, source link). The scope word '单个' (single) cleanly separates it from the batch/list sibling tpool_search_jobs.

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?

It establishes the workflow by stating job_id comes from tpool_search_jobs' items[].job_id, which tells the agent when this tool is the right follow-up call. It does not, however, spell out any when-not conditions or explicit alternatives beyond that provenance chain.

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