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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema behavior: it is served from a daily free allowance (250 left today), then $0.31 USDC on Base via x402, with no account or API key required. It says nothing about latency, output shape, or what happens when the allowance is exhausted.

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 opening question is duplicated verbatim in back-to-back sentences, which is pure waste and makes the description look machine-generated. The example request also duplicates the schema's example verbatim. Pricing is front-loaded before any functional statement of what the tool does.

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 statistical test with no output schema, the description should at least indicate what is returned (a break statistic, p-value, regime labels, etc.). It instead spends its length on pricing and a duplicated question, leaving an agent unable to predict the response or judge whether the result answers its question.

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?

There is a single required parameter (returns), so the schema carries most of the burden; its property description is truncated mid-example, so the description's full example request is a modest useful addition. It confirms the expected input form (a numeric return series) but adds no semantics such as minimum length, units, or whether the series must be chronological.

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 rhetorical question ('Did the process change, or is recent weakness inside normal variation') rather than a statement of what the tool computes or returns. The name 'regime' plus the title 'Regime Break' gives a hint, but the text never says what a call produces or what a 'regime break' result looks like, and it does nothing to distinguish this from siblings like clusteredt, drawdown, or correlation.

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 when-to-use guidance and no named alternative among the many analysis siblings. The only implicit signal is the example request, which shows a returns series as input, implying it applies to a return-stream rather than, say, a price series or an A/B setup.

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