manacher_palindrome

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

With no annotations, the description carries the full disclosure burden. It adds the notable behavioral trait of linear-time complexity via a named algorithm, which is genuinely useful context. But it says nothing about the return shape or what happens when the 'all' flag changes the output, so behavioral coverage is partial.

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?

A single front-loaded sentence with zero filler; the core action and the distinguishing algorithm both appear immediately.

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?

There is no output schema, and the description does not clarify what is returned (the substring itself vs. its length) or how the output changes when 'all' is true. For a small two-parameter computation tool this is adequate but leaves a real gap in return-value semantics.

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 100%, so both parameters (text, all) are already documented in the schema. The description adds no syntax, format, or edge-case detail beyond what the schema provides, so the baseline of 3 applies.

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 verb (Find) and resource (longest palindromic substring) and uniquely identifies the technique (Manacher's algorithm), so it is unambiguous. However, it does not differentiate itself from siblings like palindrome_check or eertree, which an agent browsing this large toolset might confuse it with.

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 only implied by the purpose itself ('find the longest palindromic substring'). There is no explicit when-to-use guidance, no mention of exclusions, and no pointer to alternatives such as palindrome_check, leaving the agent to infer the fit.

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