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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not state whether inputs must be two strings, whether the match is case-sensitive, whether an empty result is returned when there is no common substring, or what the response contains.

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?

There is nothing to trim, but the brevity is under-specification rather than conciseness. A two-clause restatement of the tool name occupies the entire description while conveying no actionable information.

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?

With no annotations, no output schema, meaningless schema labels, and a tautological description, an agent has essentially no basis for invoking this tool correctly — particularly given the unresolved a/b versus text1/text2 parameter duplication.

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 nominally 100%, but the labels are vacuous placeholders ('A to process', 'Text1 to process'), so the schema does not actually disambiguate. The description provides no help in resolving the critical ambiguity of four optional string params split into two redundant pairs (a/b vs text1/text2) with no indication of which set to populate or whether all four are required.

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 is a literal tautology, repeating the tool name twice ('Longest Common Substring: Longest Common Substring') with zero additional information. While the name itself conveys the algorithm, the description adds nothing to distinguish scope, output, or behavior from siblings like x402-common-prefix or x402-substring-between.

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?

No guidance whatsoever about when to use this tool versus its many string-similarity siblings (x402-levenshtein-distance, x402-string-similarity, x402-text-similarity). No prerequisites, no exclusions, no context.

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