jobd_status

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

Discloses blocking behavior and timeout, which is additional context beyond schema. However, no annotations exist, and the description does not mention auth needs, destructiveness, or error states. Adequate but not comprehensive.

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 sentences, no filler, front-loads the core purpose. Every sentence earns its place.

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?

No annotations or output schema; description covers basic and wait behavior but lacks details on JobInfo contents, error handling, or required permissions. Adequate for a simple read tool but could be more 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?

Adds meaning to 'wait' and 'wait_timeout_s' by explaining blocking behavior and timeout. Schema already describes clamp for wait_timeout_s, so description reinforces and connects parameters. job_id lacks elaboration, but overall good compensation given low schema coverage.

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 it gets JobInfo for a job_id, with specific behavior for wait. Distinguishes from siblings by naming the specific resource (JobInfo) and adding optional blocking behavior, though explicit sibling differentiation is missing.

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 guidance on using wait parameter (block until terminal or timeout), but no explicit instructions on when to use this tool vs alternatives or prerequisites. Useful but limited.

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