vault_install_pre_commit_hook

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

With no annotations, the description carries the full burden. It does disclose the hook's core behavior (blocks unencrypted secrets from staging), but for a mutation tool it omits critical side effects: whether install overwrites an existing hook, where the hook file is written, whether a git repository is required, and what status reports.

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?

A single front-loaded sentence that packs the action set and the tool's function with zero filler. Well-sized for a two-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?

Adequate but incomplete for a hook-mutating tool with no annotations and no output schema. The agent still cannot tell what install modifies, whether removal is safe/idempotent, or what status returns, all of which matter for correct invocation.

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%, so the description must compensate. It enumerates the three action values, effectively documenting the action enum, but says nothing about workspaceDir — what it means, whether it defaults to cwd, or what happens if it is omitted (0 required params).

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?

Names three specific verbs (install/check status/remove) against a specific resource (a zero-dependency git pre-commit hook for blocking unencrypted secrets). No sibling tool touches git hooks or staging, so the agent can tell it apart immediately.

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 three actions imply usage (install the hook, check whether it's installed, remove it), but there is no explicit statement of when to prefer this over siblings like vault_scan_workspace, nor any prerequisites (e.g. must be run in a git repo, whether an existing hook is overwritten).

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