Checks whether text is a palindrome and finds the longest palindromic substring.
Check if text is a palindrome and find the longest palindromic substring.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Text to check. |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a safe, read-only, idempotent operation with no destructive effects. The description adds no behavioral detail beyond the basic purpose, such as case sensitivity, whitespace handling, or what the result contains, which matters because no output schema is provided.
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 definition is a single front-loaded sentence with no filler. Both capabilities are stated immediately and nothing is redundant.
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 one-parameter tool, the basic purpose is covered. However, with no output schema, the description should clarify what is returned, such as a boolean plus a substring or some combined result, and it does not address edge cases like empty input or casing.
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 fully documents the single required parameter as 'Text to check,' giving a 100% coverage baseline. The description adds no additional semantics, such as whether casing or punctuation affects the palindrome determination, so it does not improve on the schema.
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 uses specific language: it checks whether text is a palindrome and finds the longest palindromic substring. This clearly distinguishes the operation from generic text utilities, though it does not explicitly differentiate itself from the sibling manacher_palindrome, which likely overlaps with the substring-finding behavior.
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 states what the tool does but gives no guidance on when to use it versus alternatives such as manacher_palindrome or reverse_text. There are no stated exclusions, preconditions, or selection criteria for the agent to follow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.