phpggc_generate

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

No annotations are provided, so the description carries the full burden. It mentions returning a PhpggcReport and that `available` is False if phpggc is missing, but fails to disclose behavioral traits like executing shell commands, security implications, or potential side effects of generating exploit payloads.

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 concise, with a clear Args section and Returns section. Every sentence is informative, and there is no redundancy.

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's complexity (5 parameters, no annotations, no output schema), the description is fairly complete. It explains inputs, output structure (PhpggcReport with payload and available flag), and a note on installation. However, it could benefit from mentioning potential risks.

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%, but the description compensates by explaining each parameter: chain (with example), command, encoding (listing options), fast_destruct (adding raw argument), and extra_args. It adds meaning beyond the schema's type/constraints.

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 starts with a specific verb ('Generate') and resource ('PHP unserialize gadget chain via `phpggc`'), clearly distinguishing the tool from its siblings which are unrelated security tools.

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 lists all parameters and explains how to use them, including a hint to run `phpggc -l` locally. It implicitly covers when to use (generating gadget chains) but does not explicitly state when not to use or provide alternatives.

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