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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true), and the description usefully adds what the tool actually surfaces — setup instructions and delivery channels (email/Telegram). It stops short of describing response shape or whether options are static vs account-dependent, which would have pushed it higher.

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?

Two sentences, no filler, and the routing constraint is placed at the end where it functions as a gate. Every clause earns its place.

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 an output schema present, the description need not explain return values, and the annotations carry the safety semantics. What remains — scope, option types, when to invoke — is fully covered for a zero-required-parameter lookup tool.

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% and the single enum parameter is fully documented in the schema, so the baseline is 3. The description echoes four of the enum values but omits 'memory', adding no syntax or mapping detail beyond what the schema carries.

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 ('Returns available options for ongoing monitoring') and enumerates the concrete option types (price alerts, idea tracking, watchlist monitoring, scheduled digests) plus channels. This lets an agent distinguish it from the informational siblings like get_market_breadth or get_price_history 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 an explicit when ('Call only when the user asks for ongoing monitoring or notifications') and an explicit when-not ('never needed to answer a question'), which is unusually strong routing guidance. The exclusion is the key discriminator against every sibling tool.

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