fomo_get_watchlist

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

With no annotations, the description carries the full behavioral disclosure burden. 'Current watchlist' only names the data and does not disclose authentication expectations, whose watchlist is returned, what items it contains, ordering, pagination, or response shape. The read-only nature is implied by the tool name rather than stated.

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 extremely short and contains no filler, but it is under-specified: a two-word noun fragment is not an adequate tool description. Conciseness is achieved at the cost of omitting useful action and context information.

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 tool with no output schema, no annotations, and a minimal description, important context is missing: what a watchlist contains, whether it is user-specific, and what the returned data looks like. The sibling list hints at watchlist operations but does not compensate for the lack of description detail.

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 input schema has zero parameters, so there is no parameter ambiguity for the description to resolve. The zero-parameter baseline of 4 applies, and the description does not need to compensate for missing schema documentation.

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 phrase 'Current watchlist' identifies the resource but lacks a verb, so the action must be inferred from the tool name 'fomo_get_watchlist'. It is minimally clear and 'current' adds a small semantic distinction, but it does not explicitly differentiate itself from add/remove watchlist siblings beyond what the name already implies.

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?

No guidance is given about when to use this tool versus fomo_add_watchlist, fomo_remove_watchlist, or any other sibling. There is no mention that this is a read-only retrieval or that it should be used to inspect the current state before modifying it. The agent must infer usage entirely from tool names.

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