cyberchef_help

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

With no annotations, the description carries the full burden. It communicates that this is a read-only catalog search and mentions filtering by keyword or category, which is useful. It does not mention output format, limits, or potential error behavior, but for a search/help tool these are minor gaps.

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 a single, well-structured sentence with no filler. It front-loads the action and resource, then lists the useful outcome categories.

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?

For a simple one-parameter discovery tool, the description covers the essential behavior: searching the catalog by keyword or category and surfacing tool and recipe capabilities. Since there is no output schema, a more explicit mention of the return shape would be ideal, but the wording is sufficient for an agent to know what to expect.

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 coverage is 100%, so the schema already fully documents the single optional query parameter. The description adds a bit of context by mentioning keyword or category filtering, but it does not materially extend the parameter semantics beyond what the schema provides.

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 verb ('searches'), a resource ('built-in CyberChef operations catalog'), and the kinds of results it returns ('available tools, supported recipe names, and operation capabilities'). This clearly differentiates it from the sibling operation tools like cyberchef_bake or cyberchef_from_base64.

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 makes it clear that this is a catalog discovery tool, which implies using it when you need to find an operation rather than execute a specific recipe. However, it does not explicitly state when not to use it or name an alternative, so usage guidance is only implied, not explicit.

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