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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds the substantive traits: no payment required, 7-day expiry, a 300-call quota, a one-per-address limit, and a returned bundle_token. That is exactly the non-obvious behavior an agent needs before committing to this enrollment, well beyond the annotation flags.

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?

Three short sentences in a deliberate order: what you get, what you must supply / constraints, what comes back and what to do next. No filler, and the value proposition plus quota are front-loaded so the agent can decide before reading requirements.

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?

There is no output schema and no annotation detail, and the description compensates by naming the return value (bundle_token) and describing how it feeds downstream tools. For a single-purpose enrollment tool with three required strings, nothing an agent needs to invoke it correctly is missing.

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 67%, so the baseline is 3. The description names the three required fields and clarifies 'the operator's work e-mail' (tying to the one-per-address rule), but it never mentions the optional plan, volume, or invoice parameters, and plan is an undescribed enum in the schema — meaning the documented edge is largely a restatement of schema descriptions.

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 ('7-day pilot with 300 calls on every TradeSignal tool and the enterprise priority slot') and explicitly contrasts itself with the paid path by naming buy_enterprise as the follow-up. An agent can tell this apart from buy_enterprise / buy_subscription without opening any schema.

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?

Gives the when ('free for teams, no wallet, no payment'), the eligibility constraint ('one pilot per address'), and the after-sequence ('pass bundle_token to get_signals and every other tool; buy_enterprise before it ends'). Both the precondition and the alternative path are spelled out rather than left to inference.

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