job

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It does not explain whether 'cancel' is destructive, whether 'wait' blocks or requires a timeout, whether 'status' and 'result' are read-only, or what side effects any action may have. The word 'lifecycle' hints at state changes, but concrete behavioral details are missing.

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 extremely short and front-loads the resource and action names, which is efficient. However, the brevity crosses into under-specification for a tool with multiple parameterized actions. It is concise but not sufficiently informative for the complexity of the tool.

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 tool with five parameters, no annotations, no parameter descriptions, and no action enum, this description is materially incomplete. An output schema exists but does not compensate for the missing guidance on how to invoke each action and which parameters are relevant. The agent would need outside knowledge to use this tool reliably.

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 coverage is 0% and the description does not map the five parameters to their purpose or to specific actions. While the description implies that 'action' accepts values like status/wait/result/review/cancel, it does not explain how job_id, agent_name, timeout_seconds, or poll_interval_seconds should be used across those actions. The agent cannot reliably construct a valid call without additional inference.

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 identifies the resource ('job') and enumerates the operations it supports ('status, wait, result, review, or cancel'), making it clear this is a job lifecycle tool. It does not explicitly state a single verb like 'manage' or 'retrieve', but the action list communicates the tool's scope effectively. It is differentiated from generic siblings by naming concrete job lifecycle actions.

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?

No guidance is provided about when to use this tool versus alternatives such as 'list', 'events', or 'delegate_task'. The action list implies usage scenarios, but there is no explicit statement of prerequisites, when to choose a particular action, or when a sibling tool would be more appropriate.

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