egx_sector_scanner

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool 'scans' and 'identifies', implying read-only behavior, but does not explicitly confirm non-destructiveness, performance implications, or authentication needs.

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 highly concise: one sentence for purpose, followed by a clean parameter list. No redundant information, every sentence is useful.

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?

Given no output schema, the description should explain the return value format (e.g., list of sectors, scores, stock picks). It only mentions 'identifies hot/cold sectors and top picks' without details on structure or data fields, leaving ambiguity.

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?

With 0% schema description coverage, the description effectively documents all 4 parameters: allowed values (e.g., timeframe options), ranges (e.g., top_n_sectors 1-18), and defaults. This adds clear meaning beyond schema titles and defaults.

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 clearly states the tool is a 'Sector rotation scanner for EGX — identifies hot/cold sectors and top picks.' This is specific and actionable. However, it does not differentiate from the sibling tool 'egx_sector_scan', which may have similar functionality.

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 on when to use this tool versus alternatives like egx_sector_scan or egx_market_overview. The description only lists parameters but lacks contextual advice about scenarios or prerequisites.

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