查看 Job 部署状态

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

With readOnlyHint=true, the description adds specific behavioral context by enumerating exactly what status information is included (current config, build attempts, successful deployment, merge status). This goes beyond the basic read-only hint without contradicting it.

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 a single concise sentence that front-loads the action (查看) and lists the exact scope. Every word contributes to the user's understanding.

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 simple tool with one parameter and no output schema, the description fully covers the purpose and scope. It clearly enumerates what the user can expect to see, making it contextually complete.

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 100%, so the description doesn't need to elaborate on the job parameter. The schema already documents it as an exact Jenkins job name with a find_job hint, which is sufficient.

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 the tool views Jenkins configuration, recent build attempts, latest successful deployment, and merge status. The verb '查看' (view) is specific and the resource scope distinguishes it from sibling tools find_job and deploy.

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 schema hint '可先用 find_job 定位' provides clear context that this tool should be used after locating the job with find_job. It implicitly distinguishes from deploy, but doesn't explicitly state when not to use it.

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