bof_postex

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

No annotations provided. The description does not disclose behavioral traits such as destructiveness, permissions required, side effects, or execution environment. The examples give minimal insight into behavior.

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 relatively concise with a one-line summary followed by examples. However, it lacks clear structure (e.g., parameter explanations) and could be better organized for quick scanning.

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, the description does not mention return values. It provides usage examples but no complete specification of what the tool returns or handles errors. Incomplete for an AI agent to reliably use.

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 has 3 parameters with 0% description coverage. The description includes subcommand syntax but does not explain agent_id or args parameters. It adds little meaning beyond the schema, leaving interpretation of command structure to the agent.

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 it's a 'PostEx-BOF: Post-exploitation utilities' and lists specific subcommands (firewallrule, screenshot_bof, sauroneye), clearly indicating it executes post-exploitation BOFs. It distinguishes from sibling bof_* tools by being the post-exploitation category, though not explicitly.

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 explicit guidance on when to use this tool versus alternatives like bof_ad, bof_creds, etc. The description only lists subcommands without context on selection criteria.

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