egx_sector_scan

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

Annotations already declare readOnlyHint=true, and the description adds behavioral nuance like 'Shows available sectors if none specified' and 'Max results per sector (max 50)'. These add value beyond annotations, though it doesn't describe output format or error behavior.

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 concise, starting with a clear one-liner, then a helpful conditional note, followed by a structured args block. Every sentence earns its place; no filler.

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 simple read-only scan tool with fully documented parameters, the description is nearly complete. It could mention the return format, but given no output schema, it's not necessary. The parameter coverage is strong.

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 bears full burden. It enriches all three parameters: lists sector examples, specifies exact timeframe values (5m, 15m, 1h, 4h, 1D, 1W, 1M), and imposes a max limit of 50. This fully compensates for the schema's lack of descriptions.

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 'Scan EGX stocks by sector' with a specific verb and resource. However, it does not differentiate from the closely-named sibling 'egx_sector_scanner', so it falls 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 provides usage context (e.g., 'Leave empty to list all sectors') but does not explicitly mention when to use this tool over alternatives like egx_sector_scanner. The usage is implied rather than explicitly contrasted.

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