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

Annotations already declare this is not read-only, not open-world, and not destructive. The description adds useful context that undeclared shell commands are invisible and that this is not a blanket approval, but it does not explain what declaration actually does, whether it grants execution rights, or how it interacts with approval workflows.

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 three short sentences, front-loads the core action, and contains no filler. Every sentence contributes either purpose, operational context, or a usage warning.

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?

Although an output schema exists and annotations cover basic safety traits, the description is too thin for a seven-parameter declaration tool with no schema parameter descriptions. An agent still lacks guidance on required fields like actionClass, resourceGlob, and iteration bounds.

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% for seven parameters, so the description carries the full burden of explaining parameter meaning. It only echoes the HIGH/CRITICAL risk enum and gives vague hints like 'for this job' and 'host action,' leaving required fields such as actionClass, resourceGlob, and jobId essentially undocumented.

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 states a specific verb and resource: declaring a HIGH or CRITICAL host action for a job. It also distinguishes the tool from a blanket approval mechanism with 'Not an approve-all,' though it does not explicitly name the sibling approval tool.

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?

Usage is implied by the warning that ToolYour cannot see undeclared shell commands, suggesting this tool should be used to make such actions visible. The 'Not an approve-all' phrase adds a partial exclusion, but the description does not explicitly say when to use this versus job_approve or related tools.

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