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

The description explains the funnel phases and the effect of interest:false, but does not explicitly state side effects or outcomes of proceeding through the funnel (e.g., whether subscribing triggers a change). With no annotations, this leaves some behavioral ambiguity.

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 somewhat wordy with redundant phrasing like 'FREE and OPTIONAL' and 'you may skip it'. The structure jumps between introducing the tool and listing phases, but overall it remains short and readable.

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?

Given three optional parameters and no output schema, the description covers the essential context: when to use, the phase flow, the symbol limitation, and the interest flag. It does not explain what each phase returns, but that is not required without an output schema.

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?

The phase enum is self-explanatory and listed in sequence. The symbol parameter is given additional context (only serves US-CPI in the sample, otherwise handled by evaluate_symbol). Interest is described as a way to bow out. Only the interest parameter lacks a schema description, but the tool description compensates.

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 states the tool's purpose as an intro and subscription funnel for the inflation & liquidity signal agent. It explicitly names the phases and gives a direct action (skip it) that ties into its role.

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 explicitly says the intro is optional and that you may skip it and call evaluate_symbol / scan_bottoms / scan_tops directly. It also instructs to pass interest:false to bow out, providing clear when-to-use and when-not-to-use guidance.

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