morse_convert

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safe pure-function profile is covered. The description adds the bidirectional behavior but omits practically important traits: how direction is inferred, handling of invalid characters, and the separator convention used in output.

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?

One short front-loaded sentence covering both directions with no filler or redundancy. Nothing could be removed without losing information.

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 single-parameter converter with rich annotations, the description is nearly sufficient, but the direction-selection mechanism is the one thing an agent must know to call it correctly and it is left implicit.

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 description coverage is 100% and the single parameter already says 'Text or Morse code to convert.' The description confirms the two input modes but adds no syntax details such as expected character set or dot/dash/space format, so it sits at the baseline.

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+resource (encode/decode Morse code) and makes the bidirectional nature explicit, which distinguishes it from siblings like rot13_convert or nato_convert. It is clear but does not explain the resources/format conventions those siblings imply.

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 implies the tool handles both directions, but never states whether direction is auto-detected or how the caller signals it. With only one input field, the agent cannot tell from the description alone when/how decoding is triggered versus encoding.

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