dhp_deny

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether a denial is final or reversible, who is permitted to deny (the parenthetical "human / policy engine" hints at the actor but is ambiguous), whether the requester is notified, or what happens if the request is no longer pending. For a state-changing operation with zero annotation coverage this is a real gap.

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?

Twelve words, one sentence, action front-loaded — nothing redundant. The parenthetical "(human / policy engine)" is too cryptic to immediately earn its place, which keeps this below a 5.

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?

An output schema exists, so return values need not be explained, but that is the only need covered. For a mutation tool with no annotations and an undocumented required identifier, the description should say something about authorization, the finality of the denial, and error conditions such as an already-decided request.

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%: approval_id has no description in the schema and the tool description never mentions it, its format, or where to obtain it (e.g., from dhp_request_approval or dhp_approval_status). The single required parameter is effectively undocumented everywhere.

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?

States a specific verb (Deny) and resource (pending approval request), which is far more informative than a bare name. It does not, however, distinguish itself from the obvious siblings dhp_approve, dhp_request_approval, or dhp_approval_status, so the agent gets the what but not the contrast.

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?

"Pending" is an implicit precondition — the agent can infer this tool applies only to requests still awaiting decision. Beyond that there is no when-to-use guidance, no when-not-to-use case, and no mention of dhp_approve as the alternative action. Usage is implied rather than stated.

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