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

Goes well beyond the readOnly/idempotent annotations: it discloses hard caps on backtracking and recursion, a structural ReDoS warning, 2 KB pattern and 200 KB subject limits, the shape of the return payload, and a per-call price of $0.005 USDC via x402 on Solana. Cost and safety-cap disclosures are exactly the behavioral context an agent needs before invoking.

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 dense paragraph that front-loads the core identity and modes before caps, limits, return shape, and pricing. Each clause carries information, though the mix of operations, constraints, and payment details in one run-on sentence is slightly harder to scan than a bulleted form.

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 output schema, the description usefully summarizes the return payload (count, matches/result/parts, engine notes) and states resource limits. However, it never explains how the caller selects match versus replace versus split or supplies flags/replacement text, leaving a real gap between described capability and the actual two-parameter interface.

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 coverage is 0%, so the description must carry parameter meaning; it only contributes size limits for pattern and subject. Worse, it advertises i/m/s/u flags, replace targets, and match/split modes that have no corresponding parameters in the schema, which will lead an agent to attempt arguments the tool cannot accept.

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?

States a specific verb and resource ('Offline PCRE2 regex tester') and enumerates the three operations it performs (match with offsets/captures, replace, split). No sibling tool overlaps this space, so differentiation is not required, but the description's claim of replace/split modes is not backed by the two-parameter schema, which muddies what the tool actually does.

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?

There is no explicit guidance on when to reach for this tool versus alternatives; it only notes that the same functionality exists over HTTPS at a given endpoint. The intended use case (testing a regex against a subject offline) is implied rather than stated, and no exclusions or prerequisites are given.

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