Encode

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

The description explicitly states the tool never mutates the vault and only returns encoded text, which aligns with the readOnlyHint annotation. This adds behavioral clarity beyond the annotation by spelling out the exact behavior.

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 two sentences, front-loaded with the core action, and contains no extraneous information. Every word serves a purpose.

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, output schema exists), the description is complete. It covers the core function and safety aspect. Minor detail about encoding specifics (e.g., standard vs URL-safe) could be added but is not critical.

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?

The input schema already has 100% description coverage for the single parameter. The description does not add any additional meaning beyond what the schema provides, so it meets the baseline but does not exceed it.

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 base64-encodes a string, specifies it never mutates the vault, and is distinct from siblings which are all vault operations. The verb 'encode' combined with the resource 'string' makes the purpose unambiguous.

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 provides the context 'with bw encode' but lacks explicit guidance on when to use this tool versus alternatives. No exclusions or when-not scenarios are mentioned, but the simple nature of the tool makes the usage fairly obvious.

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