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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the pagination/narrowing behavior of categories, count, and offset, but says nothing about ordering, freshness, or limits of the movers list; a 3 is appropriate given the annotations carry the main burden.

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 tight sentences, front-loaded with the resource and what it returns, followed by the parameter role and the routing hint. No wasted text.

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 covering return values and annotations covering safety, the description needs only purpose, params, and routing, which it supplies. It falls just short of complete because it never disambiguates against the cluster of sibling markets_* endpoints.

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%, so the schema already documents count, offset, and categories. The description restates their role ('narrow or page through results') without adding format, valid-id, or default details beyond the schema, so baseline 3 holds.

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 gives a specific verb ('Lists') and resource ('Google Finance market movers') and even names the returned fields (ticker, exchange, name). It distinguishes itself from the price-history tools but does not differentiate from very close siblings such as google_finance_markets_top, markets_trending, or markets_featured.

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 states an explicit use case ('use this for market-wide movers rather than one ticker's price history'), naming the excluded alternative. However, it gives no guidance against the many closely-named markets_* siblings, which is the harder disambiguation problem here.

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