bb_jwt_attack

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

With no annotations, the description carries the full burden. It names attack types but does not disclose behavioral traits such as whether the tool modifies the token, requires network access, or affects the system. The agent cannot infer safety or side effects.

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 very short (one line) and front-loaded with the purpose, which is good. However, it is too terse for a tool with 5 parameters and no schema descriptions, sacrificing necessary detail.

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 complexity (5 params, multiple attack modes) and lack of descriptions, the description is incomplete. It does not cover return values (output schema exists but not referenced), error conditions, or prerequisites. The agent would struggle to use this tool correctly.

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%, so the description must clarify parameters. It mentions attack types but does not link them to the 'mode' parameter or explain the role of 'public_key', 'verify_url', or 'payload_override'. Almost no added parameter meaning.

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 it performs JWT attacks, listing specific techniques (none signature, KID injection, algorithm confusion). This helps distinguish from sibling tools like bb_jwt_analyze, bb_jwt_crack, and bb_jwt_decode, though it does not explain the exact relationship.

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 guidance is given on when to use this tool versus alternatives (e.g., bb_jwt_crack or bb_jwt_analyze). The description lacks context for the agent to decide among the JWT siblings.

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