hcm_deny_write

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

readOnlyHint=false already signals mutation; the description only repeats that by saying 'Deny'. It does not disclose consequences, reversibility, permission requirements, or what happens to the pending write after denial. With no annotations beyond readOnlyHint=false, the description carries the full burden and falls short.

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?

One short sentence with the action and parameter front-loaded. No wasted words; perfectly scoped for a single-parameter tool.

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?

For a mutation with no output schema and minimal annotations, the description is underspecified. An agent is not told what response to expect, whether denial is reversible, or how this fits into the pending-approval workflow with hcm_list_pending_approvals and hcm_approve_write.

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 the description at least says the approval_id identifies the pending write to deny, going beyond the bare 'string' type. It lacks details about where the ID comes from or what format it is expected to be in.

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 uses a specific verb ('Deny') and a specific resource ('a pending write'), and identifies the key (approval_id). It is immediately distinguishable from the sibling hcm_approve_write and from read-only tools.

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 gives no guidance on when to choose this tool over hcm_approve_write or how to obtain a valid approval_id (e.g., via hcm_list_pending_approvals). It states the action but no workflow context, prerequisites, or exclusion criteria.

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