human_pause

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly covered. The description hints at cleanup and admission latching, but it never explains what gets destroyed, whether the pause is reversible, or how the two stated modes differ.

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 single sentence is brief and front-loads "Pause", but it is under-specified rather than clarifying. The "or" implies two modes, yet the structure leaves both unexplained.

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 destructive tool with an undocumented optional parameter and no output schema, the description omits critical usage, behavioral effects, and parameter guidance. It is not complete enough for an agent to call this safely or correctly.

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 schema has one optional parameter, operation_id, with 0% description coverage, and the description does not mention it at all. It adds no meaning about what operation_id identifies or when it should be supplied.

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 only immediately understandable verb is "Pause", while "cleanup barrier" and "latch admission while idle" are unexplained internal jargon rather than a specific resource or scope. The description does not clarify what is being paused or how this differs from human_stop/human_resume.

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?

There is no when-to-use guidance, no exclusions, and no comparison to sibling tools such as human_stop or human_resume. An agent has no basis for choosing this tool over its alternatives from the description.

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