bof_injection

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

No annotations are provided, so the description must fully disclose behavior. It mentions requirements for certain subcommands and lists technique numbers, but it does not discuss potential side effects, destructive actions, permissions, or error handling.

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 well-structured with separate sections for each subcommand and examples, making it easy to parse. However, it is somewhat lengthy and includes redundant formatting like line breaks that could be tightened.

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?

The tool is complex with multiple injection methods. The description covers the main subcommands but lacks details on some pool party techniques and does not mention the output schema or return format, despite one existing. This leaves some gaps for an AI agent.

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%, meaning no parameter descriptions in the schema. The description adds meaning via command examples showing how to use 'command' and 'args' (e.g., inject-cfg 808 /tmp/shellcode.bin), but it does not explicitly define each parameter's purpose or format.

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 clearly states 'Shellcode injection into target processes' and lists specific subcommands for different methods. This makes the tool's purpose explicit, though it does not differentiate from sibling tools like bof_execution which may also involve execution.

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?

The description provides examples and notes on when to use each subcommand (e.g., inject-32to64 requires 32-bit agent) but does not offer guidance on when to choose this tool over sibling tools or when not to use it.

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