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

With no annotations, the description carries the full burden and does so well: it declares read-only behavior, zero cost/no quota consumption, the exact return shape (single Markdown string), and the error contract for an invalid topic. What's missing is any hint of document size or retrieval latency, so it stops just short of fully describing the experience.

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?

Sectioned as BEHAVIOR / PRICING / USAGE / TOPICS / ERRORS with the core purpose front-loaded, so an agent can skim. The TOPICS list and PRICING block add bulk, but each entry maps to a real decision the caller must make, so little is pure filler.

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 one-parameter lookup tool with no output schema, the description covers purpose, exclusions, valid values with meaning, cost, return type, and failure mode. An agent has everything needed to invoke it correctly on the first try.

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 already 100% with an enum, so the baseline would be 3; the description earns above that by glossing each topic value (e.g. 'calculators' = position sizing, true MMR liquidation, DCA break-even), which lets an agent pick a chapter without guessing from the label alone. The glosses are brief and the labels are largely self-descriptive, keeping it off a 5.

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: reads and returns official BitCLI markdown specifications for formulas, CLI guides, and webhook setups. The read-only RAG framing plus the return type (a single Markdown document string) makes it unambiguous and clearly distinct from siblings like market_data or alert_manager.

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?

Explicitly says to use this tool FIRST to learn BitCLI mechanics or verify command grammar, and explicitly excludes live price/active-trigger queries by naming the alternatives (market_data, alert_manager). Both the when and the when-not are stated with the substitute tools.

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