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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by enumerating the returned statistics (confidence intervals, q-values, verdicts, timing quartiles, citation URL), but says nothing about failure modes for an unresolved pattern id or response size, so it is useful context rather than rich behavioral disclosure.

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 sentence with the purpose front-loaded and the return contents following. It is dense but every clause names concrete data the agent will get; the colon-separated enumeration is slightly list-heavy but not padded.

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 must describe what comes back, and it does so concretely down to q-values, timing quartiles, and a citable page URL. The main remaining gap is error behavior when the pattern identifier does not resolve.

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% and enums are supplied for side, market, and timeframe, so the schema carries the parameter burden. The phrase 'every market, timeframe and breakout side measured' reinforces that these are filter dimensions over a full result set, but adds no format or default semantics beyond 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?

States a specific resource and scope: 'Full tested results of one pattern', enumerated as detection rule, trade rules, and per-market/timeframe/side measurements. The 'one pattern' framing implicitly sets it apart from compare_patterns and search_patterns, though no sibling is named explicitly.

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 when-to-use statement, no exclusions, and no reference to the obvious alternatives (search_patterns to find a pattern, compare_patterns for multi-pattern comparison). The single-pattern scope is only implied by the title and description text.

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