remove_hooks

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

With no annotations, the description must fully disclose behavior. It implies a destructive/mutating action but lacks details on side effects, such as whether all hooks are removed or if persistent hooks are affected (though the parameter suggests otherwise). No mention of required states or consequences.

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 very concise (one sentence) and front-loaded. However, it sacrifices essential information about parameters and usage, making it too terse for a complete specification.

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?

Given the presence of one parameter, no output schema, and no annotations, the description is insufficient. It does not explain the parameter, provide usage context, or mention return values. The agent would lack guidance to invoke the tool 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 1 parameter (keep_persistent) with 0% description coverage, so the description should explain its meaning. It does not. While the parameter name is somewhat self-explanatory, the agent lacks explicit guidance on how it affects behavior.

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 action ('Remove installed hooks') and the result ('restore original objects'). It uses a specific verb and resource, distinguishing it from sibling tools that add hooks or manipulate them.

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?

No guidance is provided on when to use this tool versus alternatives like hook_function or inject_hook_preset. There is no mention of prerequisites, context, or when removal is appropriate.

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