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

Annotations already establish readOnlyHint=true, so the safe-read nature is covered. The description adds meaningful context beyond annotations: the content is historical research, non-predictive filing notices, failed and killed ideas, and never individualized recommendations. This helps an agent set expectations and avoid over-interpreting output, which goes beyond simple read-only metadata.

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 description is front-loaded with the core use case and ends with an important limitation phrase. It packs a lot into one long sentence and a few follow-ups, and while the first sentence is a dense list, every clause contributes a distinct navigation path or boundary. It is organized and readable, though slightly verbose with several overlapping categories.

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 cannot rely on structured output documentation, but it still supplies enough domain boundary, mode routing, and caveats for an agent to call the tool appropriately. It does not detail exact return shapes, but for a read-only record-and-notice tool with three optional parameters, this is sufficient guidance.

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 100%, so the baseline is fair at 3. The description adds semantic meaning to the enum modes themselves: overview as the validated strategy and governance record, open as detections, notices as non-predictive filing boards, etc. The schema alone would expose only opaque mode names, so this is a clear value-add.

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 opens with a specific directive: "Use this for any question about Boothcheck strategies, signals..." It names a clear resource and scope, and the mode list (overview, open, history, signals, notices, graveyard) tells an agent exactly what domain it covers. This distinguishes the tool from its siblings, which appear to cover pricing and coverage rather than strategy records.

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?

The description gives explicit guidance: use this tool for Boothcheck strategy/signal questions, and it even says "never individualized recommendations." It also maps each mode to its use case, e.g., "graveyard for failed research." It does not explicitly name sibling tools as alternatives, but it clearly defines the tool's territory and a notable when-not case.

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