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

With annotations only marking it as a write (readOnlyHint=false), the description carries substantial extra load: a 48-hour processing window, the two possible outcomes (built as a ticker or a posted rejection reason), a dedicated response URL, the fact that submissions are never shown publicly, a 3-per-day rate limit, and 'Free'. This is exactly the behavioral context annotations cannot supply.

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?

It is long, but front-loads the trigger condition and every subsequent sentence adds a distinct behavioral fact (timeline, outcomes, privacy, rate limit, cost). There is mild redundancy in the closing marketing line about /launch, but overall it is dense and well-ordered.

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 submission tool with no output schema, the description covers what happens after the call, the return value ('count of numbers named so far'), rate limits, privacy, and cost. An agent has everything needed to set expectations and call correctly.

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%, so the parameters are already documented. The description mostly restates the schema (one line, 3-160 chars, source location, ticker format) rather than adding new meaning; it also loosely says '2 to 12 letters or digits' where the schema allows maxLength 13, a minor mismatch. Baseline 3 is appropriate.

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 clearly frames this as a request/submission tool for counts Tickerz does not yet publish, and even equates it to POST /api/indices/requests. It distinguishes itself from siblings like get_index/list_indices by targeting unpublished numbers, though the core verb ('request a new ticker to be built') is conveyed narratively rather than stated crisply up front.

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?

It gives an explicit trigger ('when someone wants a number counted that Tickerz does not publish yet, or a market needs a number nobody sells') and names an alternative route for on-chain counts via /launch. The condition that selects this tool over alternatives is spelled out, not inferred.

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