program_scope_deny

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

No annotations are provided, so the description carries the full burden. It discloses the key behavior: blocking even if in scope. However, it doesn't mention permanence, reversibility, permissions, or how this interacts with other scope operations. The description adds minimal but important behavioral context beyond the name.

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 a single concise sentence that is correctly front-loaded with the action. It earns its place by stating the core behavior. However, the typo 'if if' slightly reduces its polish and precision.

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?

The tool is simple with one parameter and no output schema, yet the description is minimal. It explains the effect but omits context about how deny relates to allow, whether it's persistent, or what happens to the target's scope status. Given the presence of scope management siblings, a bit more context would be beneficial.

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?

The input schema has one parameter 'target' with no description (coverage 0%). The description only says 'deny a target,' which merely repeats the parameter name. It does not explain what format or type of target is expected (e.g., IP, domain, URL), so the description fails to compensate for the schema's lack of documentation.

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 the tool's function: to explicitly deny a target, overriding its in-scope status. The verb 'deny' is specific, and the resource is 'a target.' It distinguishes from siblings like program_scope_allow or scope_add by emphasizing the explicit denial even when in scope.

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?

The description implies when to use the tool: when a target is in scope but needs to be blocked. However, it does not explicitly mention alternatives or provide exclusions. There is no guidance on when not to use it or how it differs from scope_remove or program_scope_out_of_scope.

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