empire_modules

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

No annotations provided. The description claims the tool is for searching and viewing, but the schema allows executing modules on agents, which is a significant behavioral trait not disclosed. This misrepresentation reduces transparency.

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), but it omits important functionality (execute). It is front-loaded but inaccurate, so conciseness does not compensate for completeness.

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 5 parameters including a nested object and no output schema, the description is too sparse. It does not explain the difference between actions, required fields for execute, or anything about the options object.

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 schema already explains each parameter adequately. The description adds minimal value beyond the schema, not clarifying nuances like the relationship between action and other parameters.

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 'Search and view', but the action enum includes 'execute' (and 'get'), which goes beyond search and view. This omission makes the purpose unclear and potentially misleading. It does not fully describe what the tool does.

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 on when to use this tool versus siblings like empire_shell or empire_agents. There is no mention of prerequisites, when to use each action, or exclusions.

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