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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds value beyond that by disclosing the return payload (converted output, original input, character length) and a explicit cost of 1 credit, which the annotations do not convey.

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?

Two sentences, front-loaded with the capability and followed by the invocation contract and cost. The only waste is the redundant repetition of the tool name at the start, which is minor enough not to lower the score.

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 two-parameter, read-only conversion utility with only one required input, this covers everything an agent needs: what it does, how to call it, what comes back, and the credit cost. An output schema exists, so the return-value detail is bonus rather than a gap.

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 100%, so the baseline is 3, but the description goes further: the schema only says 'The action to perform' with no enum, and the description supplies the actual legal values (encode/decode). It also clarifies that the input string may be either plain text or an encoded string, resolving the ambiguity in the schema's 'The text to encode' wording.

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 states a specific verb and resource ('encodes plain text into Base64 and decodes encoded strings back to readable characters'), which is unambiguous. It does not distinguish itself from adjacent siblings such as ASCII85Encoder, URLEncoderDecoder, or HTMLEntitiesEncoderDecoder, which is the only thing keeping it from a 5.

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?

It tells the agent to 'submit any string with an encode or decode action', which implies the invocation pattern, but gives no when-to-use guidance and never mentions that other encoder/decoder siblings exist for different formats. Usage is inferable rather than directed.

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