Encode

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

The description reaffirms the read-only nature indicated by annotations, adding that it "only returns encoded text." However, it lacks details about output format, error conditions, or limitations.

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 extremely concise—two sentences that efficiently convey the tool's action and behavioral constraint with no unnecessary words.

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 encoding tool with one parameter and an output schema, the description covers the essential purpose and safety. It could optionally mention that the encoded output is a string, but overall sufficient.

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 single parameter 'value' is already fully described in the schema as "Plain text value to base64-encode." The description adds no extra semantic information 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 clearly states that the tool "Base64-encode[s] a string" and specifies it never mutates the vault, distinguishing it from sibling tools that create or modify vault items.

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 explicit guidance on when to use this tool versus alternatives, such as other encoding or transformation tools. The description is purely factual without contextual recommendations.

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