base64_decode

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

No annotations are provided, so the description carries the full disclosure burden. It reveals the output encoding (UTF-8) but says nothing about behavior on invalid base64, non-UTF-8 bytes, or whitespace/padding handling; the trailing '[conductor: verified pure command]' tag is internal noise rather than useful behavior context.

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 functional sentence is front-loaded and wastes nothing. The bracketed conductor tag is extraneous metadata that dilutes an otherwise tight definition.

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 one-parameter utility with no output schema, the description does supply the return type (UTF-8 text). However, it omits error behavior for malformed input and the fact that non-UTF-8 payloads cannot be represented, which are the main things an agent needs to call this 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 coverage is 0% and the single parameter `encoded` is undocumented in the schema, but the description does say the input is a base64 string, which adds meaning about expected content. It adds no detail about padding, whitespace, or encoding variants.

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 (decode) and resource (base64 string) plus the output format (UTF-8 text), which cleanly separates it from the sibling base64_encode. It only stops short of 5 because it never names the inverse operation as the tool to avoid.

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?

There is no explicit when-to-use statement, prerequisite, or alternative named. Usage is only inferable from the verb, which the rubric treats as no real guidance.

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