list_jobs

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

Discloses important behavioral details: closed jobs not unchecked 'cancel display on website' are still returned, and deleted jobs are not. This adds context beyond the schema. No annotations provided, so description carries full burden.

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?

Concise and well-structured with bullet points for parameters and behavioral notes. It includes the API endpoint for reference without unnecessary fluff. Could be slightly more streamlined.

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?

Covers all necessary context: required parameter, optional parameters with defaults, and edge case behaviors. With an output schema existing, it appropriately omits return value details.

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?

Despite 0% schema description coverage, the description explains each parameter clearly: mode is required with enum values, org_id defaults to environment variable, limit sets max results. This adds significant value over the schema definition.

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?

Clearly states '查询职位列表' (query job list) and specifies the Moka API endpoint. It distinguishes from sibling tools like get_job_detail and list_departments by its focus on listing jobs with specific filters.

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?

Provides parameter details and behaviors for edge cases, but lacks explicit guidance on when to use this tool versus alternatives like search_candidates or get_job_detail. The description assumes the user knows to use it for listing jobs.

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