text_duplicate_line_remover

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

Without annotations, the description carries full burden. It discloses key behavioral features: preserving order or applying sort, case-sensitive/insensitive matching, and whitespace control. This goes beyond what the empty schema provides, though it omits performance or side-effect details.

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 brief but includes a 'Menu ID' that is likely irrelevant for API usage. It is not overly verbose but could be more focused on actionable guidance.

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?

Given the empty input schema, no output schema, and no annotations, the description should explain how to provide input and what to expect as output. It only describes behavior but not invocation details, forcing reliance on an external describe_tool. The agent lacks enough context 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 input schema is empty with additionalProperties:true, providing no parameter definitions. The description does not clarify how to pass text or set options (order, case, whitespace), leaving the agent with no guidance on invocation syntax. Schema coverage is 100% because there are no properties, but the description fails to compensate for the lack of parameter information.

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 removes duplicate lines from text with options for order preservation, sorting, case sensitivity, and whitespace control. However, it does not explicitly differentiate from sibling tools like text_duplicate_word_remover or text_sort_lines, though the name makes the purpose clear.

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 usage for removing duplicates but gives no explicit when-to-use or when-not-to-use guidance. It references describe_tool for full guidance, which suggests the description is not self-contained.

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