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

Annotations only declare readOnlyHint=true, but the description adds crucial behavioral rules: quote prices, plans, dates and topics only from this result; a null field means the part could not be loaded and must be reported as such, never guessed. It also discloses that UTC times carry pre-converted Eastern twins (scheduledAtEastern, endDateEastern) that should be quoted, which is real operational context an agent cannot infer.

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?

Four tight sentences, front-loaded with purpose, then trigger conditions, then data-integrity rules, then timezone guidance. No filler, and each sentence carries a distinct instruction the agent needs.

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 no output schema and no parameters, the description carries the burden and does so: it names the fields the agent will encounter (scheduledAtEastern, endDateEastern), states how to treat nulls, and constrains quoting to returned data. Nothing needed to call or report on this tool 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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description does not need to compensate for any schema gap.

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—'Live facts about the AI Trading Bootcamp and the free live challenge show, read from the database'—and enumerates the concrete subject matter (price, payment plans, curriculum, dates, next show time). No sibling tool covers this domain, so the purpose is unmistakable at a glance.

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 explicit triggering conditions: user asks about the Bootcamp, its price/plans/curriculum/dates, the free live challenge or its next date, or a new/stuck user asking how to learn AI trading. Strong on when-to-use, but offers no when-not-to-use conditions or named alternatives (none exist among siblings, which softens the gap).

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