aiworkhub_dashboard_storage_registration_prune

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 discloses that the tool is a USER WRITE, refuses when foreign stale registrations exist or the digest drifted, runs git worktree prune, records an audit entry, and invalidates storage telemetry — exactly the behavioral context an agent needs for a mutating storage operation.

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?

Two tight sentences, front-loaded with the action and scope, followed by prerequisites, alternatives, and refusal conditions. Every clause earns its place by adding an operational constraint or destination 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?

Given a mutating storage tool with no annotations but a full output schema, the description covers the required prerequisite, confirmation gate, refusal conditions, side effects, and alternative tool. It is complete enough for an agent to act safely without needing the output schema to explain returns.

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 100%, so the parameter semantics are already well documented in structured fields. The description reinforces that preview_digest comes from the preview tool and that confirm must be True, but it does not add syntax, format, or constraint details beyond what the schema already provides.

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 and resource: pruning stale AIWorkHub Git worktree registrations. It adds the key qualifier that pruning is verified against a current preview digest, and explicitly distinguishes the action from physical directory quarantine.

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?

Explicitly instructs the agent to call aiworkhub_dashboard_storage_retention_preview first to obtain the digest, and names aiworkhub_dashboard_storage_quarantine as the alternative for moving physical worktree directories. It also states the confirm=True requirement, leaving little ambiguity about when and how to invoke it.

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