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

The annotations already set destructiveHint: true. The description adds that delete_file requires confirm=true and is HITL, but overall it does not disclose other behavioral traits like what happens on failure, authorization needs, or side effects for the many actions. The sub-action descriptions are brief and lack detail.

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 a lengthy list of 19 sub-actions with inline parameter docs. It lacks front-loading of key information and is not concise for an AI agent. Many sentences could be consolidated or referenced from structured metadata.

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?

Despite having an output schema (not shown), the description does not explain return values, error handling, or how to correctly structure the params object per action. For a complex tool with many sub-actions, more detail is needed to ensure 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 description coverage is 0%, so the description must compensate. It lists each action with its parameters (e.g., 'lock - params: {path}'), which provides meaning beyond the minimal schema. However, the params object is not formally described, and the agent must infer valid properties per action. It adds partial value but is not comprehensive.

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 states 'Governance, Hypervisor & security tools for the Nucleus Agent OS.' but the tool itself is a generic dispatcher for many sub-actions (e.g., lock, delete, compliance). It fails to distinguish from siblings like nucleus_audit or nucleus_plan_execute, which have specific purposes. The purpose is too broad and not centered on a clear verb+resource.

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 sibling tools. The description lists sub-actions but does not explain the context or conditions for invoking them, nor does it offer alternatives for overlapping functionality.

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