Echo text

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

No annotations are provided, so the description carries the full burden. It transparently states the behavior: returning text and optionally adding a prefix. It does not explicitly state that the operation is read-only or side-effect-free, but 'return' strongly implies it, which is adequate for this simple tool.

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 a single, front-loaded sentence with zero redundancy. It efficiently communicates the core action and the optional parameter.

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 tool with only two simple parameters and no output schema, the description is nearly complete. It explains what the tool does and the role of the optional prefix. Minor ambiguity remains about the exact formatting of the prefix, but overall it gives an agent enough to use the tool correctly.

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 0%, so the description must compensate. It mentions that prefix is optional and implies it is prepended to text, providing meaning beyond the schema. However, it doesn't detail how the prefix is concatenated (e.g., spacing or order), which is left to the caller.

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 action: 'Return text to the caller' with an optional prefix. This clearly identifies the tool's function and distinguishes it from the sibling 'server-time' which is about time retrieval.

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?

Usage is implied by the description—if you need to echo text with an optional prefix, this is the tool. However, there is no explicit mention of alternatives, when not to use it, or comparison with sibling 'server-time', so it only meets the 'implied usage' bar.

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