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

No annotations are provided, so the description carries the transparency burden. It usefully reveals that original order is preserved, but it does not specify exact duplicate matching (e.g., whitespace/case sensitivity), blank-line handling, or whether the result is returned as new text.

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 communicates the full operation and a meaningful behavioral guarantee without any filler. It is front-loaded and every word earns its place.

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 utility with no output schema, the description is nearly sufficient: it tells the agent what happens and the ordering guarantee. It stops short of explicitly stating the return value and edge-case behavior, but those are reasonably inferable for this transformation.

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 for the bare text parameter. The word 'lines' gives the key semantic that text is treated as a line-oriented string, which the schema does not state, but details like line delimiters and formatting are not provided.

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 operation — removing duplicate lines — on a specific resource (text), and adds a clear ordering guarantee. This is easily distinguishable from the sibling tools, none of which appears focused on line deduplication.

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 when to use the tool: whenever a user needs duplicate lines removed while keeping order. It does not explicitly name alternatives or state when not to use it, leaving some routing inference to the agent.

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