text_flip

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

With no annotations, the description carries the full burden of behavioral disclosure. It defines the three modes and their effects, which is the core behavior. However, it omits edge-case behavior such as how line breaks are handled in 'full' mode (are they reversed in character order?), and whether 'line' mode preserves newline characters. These gaps are notable for a text transformation 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 sentence that front-loads the purpose ('文本翻转/倒序') then uses semicolon-separated mode definitions. It is concise, well-structured, and contains no filler. Every word serves to clarify the tool's behavior.

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 tool with two parameters and no output schema, the description covers the essential information: it defines the modes and their outputs. It does not explain return value formatting, but that is implied for a text transformation. Minor gaps like newline handling prevent a perfect score, but overall it is sufficiently complete for an AI agent 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?

The schema has 0% description coverage for parameters. The description compensates by explaining the meaning of each enum value for 'mode' (full, line, reverse_lines), which is the key parameter. The 'text' parameter is self-explanatory as the input string. This adds significant value beyond the schema's enum definition and default.

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 the tool's function with a specific verb ('翻转/倒序' = flip/reverse) and resource (text). It goes beyond the name by explaining three distinct modes (full, line, reverse_lines), which differentiates it from sibling text tools like text_format or text_replace. Each mode is explicitly defined, making the purpose unambiguous.

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 provides no guidance on when to choose this tool over alternatives. It explains how to use the 'mode' parameter but does not contrast with sibling tools or state use cases. For example, it does not say 'use this to reverse entire text' versus 'use text_filter for filtering'. Thus, usage context is implied rather than explicit.

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