empire_stagers

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It merely states 'Generate and manage' without explaining what happens during creation (e.g., listener requirement, network impact), safety, or destruction. This is insufficient for a tool with multiple actions including delete.

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 single, concise sentence with no redundant words. However, it could be slightly more informative (e.g., listing supported actions) without becoming verbose, so it gets a 4 rather than a 5.

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 tool has 6 parameters, 5 actions (including delete), and an actions-based workflow, the description fails to tie these together. It does not explain that 'action' determines behavior or that a listener is required for creation, leaving the agent underinformed.

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 input schema has 100% description coverage for all 6 parameters, so the schema already documents parameter meaning. The description adds no extra context beyond the schema, fitting the baseline of 3.

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 provides a verb+resource: 'Generate and manage stagers/payloads for Empire agents,' which is clear and distinguishes the tool from siblings like empire_agents or empire_listeners. However, it does not explicitly differentiate from similar tools like empire_modules or empire_profiles, so it falls short of a perfect 5.

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 guidance on when to use this tool versus its siblings. The description does not mention when to choose empire_stagers over empire_agents or empire_listeners, leaving the agent without context for selection.

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