get_job_detail

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 content returned (職務說明、條件、薪資、地點) but does not mention any behavioral traits like read-only nature, authentication requirements, rate limits, or potential errors. This is adequate for a read operation but could be more transparent.

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 description is two sentences: one clearly stating the tool's function and the second explaining the parameter source. Every word earns its place, with no redundancy or unnecessary detail, making it highly efficient and front-loaded.

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?

Given the tool's simplicity (1 parameter, no output schema) and sibling tools, the description is fairly complete. It explains what the tool does and where the input comes from. It could be more explicit about the return format, but listing the content areas (job description, conditions, etc.) provides sufficient context.

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?

The parameter 'detail_id' has 0% schema coverage, meaning the schema provides no description. The tool's description compensates by explaining that the ID comes from 'search_jobs' results, adding crucial semantic context beyond the raw schema. It does not specify format or constraints, but the origin is valuable.

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 it retrieves full content of a single job listing, specifying details like job description, conditions, salary, and location. It also distinguishes itself from the sibling tool 'search_jobs', which lists jobs, making the purpose unambiguous.

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 description explicitly states that the 'detail_id' comes from 'search_jobs' results, providing clear context for when to use this tool (after a search). However, it does not explicitly mention when not to use it or suggest alternatives beyond the implied dependency.

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