exploit_smb

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

The description uses 'Check' suggesting a read-only operation, but the tool name 'exploit_smb' implies potential exploitation. The default 'check_only: true' in the schema hints at safe behavior, but the description does not clarify the tool's actual side effects or whether it performs any exploitation by default. With no annotations, the agent lacks clear behavioral context.

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 extremely concise (one sentence), but this brevity comes at the cost of essential details. It is front-loaded but lacks structure or segmentation.

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 two parameters and no output schema or annotations, the description fails to provide a complete picture. There is no information about return values, error handling, or expected outcomes, leaving the agent with substantial ambiguity.

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%, and the description provides no explanation for the two parameters ('target_ip' and 'check_only'). The agent cannot infer what the IP address is for or what 'check_only' entails beyond its boolean nature.

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 a specific action ('Check SMB vulnerabilities') and a concrete example ('EternalBlue, etc.'), which clearly identifies the tool's focus on SMB vulnerability assessment. However, it does not explicitly differentiate from sibling tools like 'run_network_exploit' or 'run_exploit' that may also target SMB vulnerabilities.

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 the many sibling exploit or scanning tools. There is no mention of prerequisites, limitations, or scenarios where an alternative would be more appropriate.

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