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

Annotations already cover the safety profile (readOnly, non-destructive, open-world). The description adds real behavioral value: bounded thread pool, the fact that unservable rows go to `skipped` and are 'never silently dropped,' and what is attached per row. This is meaningful disclosure beyond the annotations, though nothing is said about latency or rate-limit implications.

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?

Front-loaded with the one-line purpose, then supporting workflow detail, then a compact args block. Every sentence earns its place; only minor slack in restating defaults that also appear in the schema.

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, the description does the needed work by explaining what each returned row contains (volume-flow composite score, banker decomposition, oscillator state) and how failures surface via `skipped`. Complete enough for correct invocation; only the exact ranking/tie-break semantics are unspecified.

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%, so the description carries the full burden and does so: it enumerates the index values, gives the default and max for `limit`, the window options for `period`, and the 0-100 range for `min_score`. Without this text the parameters would be opaque.

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 scope: 'Rank EGX index constituents by smart-money accumulation evidence,' which is clearly distinct from the single-symbol smart_money_analysis sibling. It does not explicitly name or route against siblings like smart_volume_scanner, so it stops short of a 5.

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?

The description implies usage by describing the underlying workflow ('runs the full smart_money_analysis per constituent'), so an agent can infer this is a batch/index-level scan rather than a single-symbol call. However, it never states when to choose this over smart_money_analysis or smart_volume_scanner, nor any exclusions or prerequisites.

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