set_job_priority

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

The description lacks any behavioral traits beyond the action itself. There is no mention of side effects, limitations, permissions, or whether the change is immediate or reversible. With no annotations provided, the description fails to disclose important behavioral aspects.

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?

While the description is concise (one sentence), it is underspecified and lacks structure. It does not earn its place as it provides minimal helpful information.

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 complexity (mutation, integer parameters) and no output schema details, the description is incomplete. It does not explain return values, success conditions, or behavior for invalid inputs.

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 0%, yet the description adds no meaning to the parameters. It does not explain what 'prio' means (e.g., valid range, effect) or what 'job_id' refers to. The description is insufficient to aid agent understanding.

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 'Set the priority of a job.' uses a specific verb and resource, clearly indicating the action and target. It distinguishes from sibling tools as no other sibling explicitly sets job priority.

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 on when to use this tool versus alternatives, such as when jobs can have priorities set, or any prerequisites. No exclusions or contexts are mentioned.

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