get_market_watch

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

With no annotations, the word 'snapshot' and 'whole-market' convey that this is a point-in-time read over a broad market scope and that bulk fetching is intended. However, it does not disclose response shape, pagination, or potential side effects, leaving some behavioral burden unmet.

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 compact sentences carry purpose, scopes, and a usage preference with no filler. The key concept is front-loaded and every clause adds 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, the description fails to describe what the snapshot contains, how 'top' limits results, or what 'flow' means; it also references an absent 'market' parameter. The agent cannot reliably construct a correct call from this description alone.

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 0%, yet the description only documents a 'market=' value set that does not match the actual schema properties 'top' and 'flow'. It adds some domain meaning for market segments but leaves both declared parameters essentially unexplained and may mislead an agent looking for a market parameter.

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 opening phrase 'Whole-market snapshot' gives a clear verb-resource pair, and the parenthetical enumerates the market scopes (all, bourse, fara-bourse, payeh), so an agent can distinguish it from per-symbol tools. It does not explicitly differentiate it from market_status or get_index_overview, but the whole-market watch concept is clear.

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?

'Prefer this over per-symbol loops' states the intended use case and warns against an inefficient alternative. It does not name sibling tools or state when NOT to use it, so it earns a 4 rather than a 5.

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