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

Beyond the read-only and idempotent annotations, the description discloses important behavioral details: letters separated by spaces, words by forward slashes, underscores treated as dashes when decoding, pipes as word separators, and unknown Morse sequences rendered as '#'. This gives the agent concrete expectations about input normalization and output formatting.

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 compact and front-loaded: the core purpose appears first, followed by three high-value formatting details and a source link. Every sentence contributes operational information, with no filler or repetition of schema content.

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 deterministic two-parameter converter, the description covers the essential behavior: direction, separators, decoding aliases, and unknown-symbol handling. The annotations already convey safety and idempotence, and the presence of an output schema means return-value documentation is not required here.

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%, with both 'text' and 'direction' already documented. The description adds semantic value by explaining Morse input/output conventions, such as separator characters and alias handling, which go beyond the schema's generic 'text or Morse code to translate' phrasing.

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 opens with a specific verb and resource: 'Translate text into international Morse code, or Morse code back into text.' It names the exact conversion domain and bidirectional behavior, making the tool's purpose immediately obvious and distinct from sibling text-manipulation and encoding tools.

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 clearly states the two use cases: text-to-Morse and Morse-to-text. It does not explicitly name alternatives or state when not to use the tool, but the specificity of 'international Morse code' and the bidirectional wording provide enough context to select this tool correctly among many sibling converters.

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