websex_ghidra

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that argv tokens are passed directly without shell parsing (an important invocation-safety trait) and that it runs from the engagement namespace, but it says nothing about side effects, permissions, or what happens on failure.

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?

Three tight sentences, front-loaded with the action and the safety-relevant argv detail. No padding or repetition of the name.

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?

An output schema exists, so return values need not be explained, and the argv/namespace notes are helpful. But for a tool that runs an arbitrary external binary, the description omits permission expectations and how stdin/working_directory interact with the engagement scope, leaving it only minimally adequate.

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% across 4 parameters, so the description must compensate and largely does not. It clarifies that 'arguments' are argv tokens and hints at the engagement namespace and working directory via relative paths, but it never addresses the 'stdin' parameter, leaving a required input path undocumented.

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?

States a specific verb and resource ('Run ghidra from the WebSex binary toolkit'), so an agent knows it invokes the Ghidra reverse-engineering tool. However it offers no differentiation from closely related siblings such as websex_radare2, websex_objdump, or websex_angr_analyze, leaving tool selection ambiguous.

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 gives no guidance on when to prefer Ghidra over radare2, objdump, or the other analysis siblings, and states no prerequisites. The only usage-adjacent hint is 'use relative paths for engagement artifacts,' which is about path handling, not tool selection.

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