bb_jwt_decode

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

The description explicitly states the tool does not verify the signature, a critical behavioral trait. With no annotations provided, this disclosure is valuable. It does not elaborate on error handling or output format, but the output schema covers that.

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 concise sentence, front-loading the tool's purpose and key behavior (no signature verification). Every word earns its place.

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 simplicity (one parameter), the presence of an output schema, and the description covering the main purpose and critical non-verification behavior, it is fairly complete. It could add a note about what the output contains, but the schema likely handles that.

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?

With 0% schema description coverage, the description adds minimal meaning beyond the schema: it explains that the token is a JWT and that the tool decodes it. It does not describe token format, constraints, or the output structure.

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 the tool decodes a JWT and parses the header and payload without signature verification. This distinguishes it from sibling tools like bb_jwt_verify or bb_jwt_attack, though explicit sibling differentiation is absent.

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 implies usage when a JWT's contents need to be inspected without verifying the signature, but does not explicitly state when not to use it or provide alternatives. The non-verification trait provides some guidance.

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