job_start

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

Discloses async nature, write operation, inverse relationship, and polling expectation. With no annotations, description carries full burden and does well, though could add more on permissions or side effects.

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?

Efficiently uses three lines: headline with WRITE flag and purpose, async note, inverse, polling advice, then args. No filler, front-loaded key info.

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 async behavior and progress tracking via session tools, plus inverse operation. No output schema, but explanation suffices. Missing error handling or duplicate call behavior, but adequate for the complexity.

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%, but description adds meaning: job_id is 'Veeam job id' and target is 'Veeam target name from config'. This goes beyond schema labels, though more detail (e.g., format, validation) would improve.

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 '[WRITE] Start a backup job' with a specific verb and resource, and distinguishes from siblings like job_stop and session_list. It also notes async execution, making the tool's purpose unambiguous.

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 explicit when to use (start a job), inverse operation (job_stop), and important guidance: do not re-issue, poll with session_list/session_get. Missing explicit when-not-to-use for alternative scenarios, but sufficient for typical use.

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