tools_fierce

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

With no annotations provided, the description must disclose behavior, but 'Execute fierce.' provides zero information about side effects, required privileges, output format, or potential impact. The agent cannot infer whether this is a safe read-only operation or a destructive one.

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?

While the description is maximally concise, it is under-specified to the point of uselessness. 'Execute fierce.' conveys no meaningful information, so brevity is not a virtue here.

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?

For a tool with two parameters, no output schema, and no annotations, the description provides essentially no context. An agent would have to guess the tool's purpose, argument semantics, and expected results.

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 defines domain and additional_args, but the description does not explain their meaning or usage. With 0% schema coverage, the description should compensate, but it offers no parameter guidance whatsoever.

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 'Execute fierce.' merely restates the tool name with a generic verb. It does not indicate what 'fierce' does (e.g., DNS enumeration) or what resource it operates on, failing to distinguish it from sibling tools like tools_nmap or tools_gobuster.

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 alternatives. The description lacks any context about target scenarios, prerequisites, or exclusions, leaving the agent without decision support.

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