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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, and the description adds real behavior beyond them: an unknown sector falls back to returning the sector directory instead of erroring, and the data is a free sample drawn from the morning read, which signals staleness relative to the live sibling. What it omits is any statement about result size limits/pagination, but the sample-size constraint is disclosed.

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 return shape is front-loaded well, but the opening two sentences overlap heavily ('which stocks lead it' repeats 'the top 3 member stocks ranked by opportunity'), and 'for trading with the money rather than against it' is marketing filler that does not help an agent act. Trimming to two tight sentences would lose no 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?

With no output schema, the description carries the burden of describing the return surface, and it does so: top 3 members, member count, count of members by state, and the sector's own ETF row. Combined with the single well-documented parameter and fully covering annotations, an agent has enough to call this correctly; only the live-versus-delayed relationship to the sibling remains unstated.

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 coverage is 100% for the single parameter, so the baseline would be 3; the description earns more by supplying concrete accepted forms (sector names such as 'Energy' and 'Information Technology', ETF symbols such as XLE and XLK) and the fallback behavior for values it does not recognize. This meaningfully reduces the chance of a malformed call.

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 states a concrete verb+resource: a single sector's trend drill-down with top 3 member stocks ranked by opportunity, member count, count by state, and the sector's ETF row. It is clearly scoped and distinguishable from get_stock_read / get_board_* siblings, and the 'morning read' phrasing implicitly separates it from get_sector_read_live, though the live/non-live split is never made explicit.

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 tells the agent what input shapes are accepted (sector name like 'Energy' or ETF symbol like XLE) and that unknown values return the sector directory, which is genuine usage guidance for query construction. However, it never says when to choose this over get_sector_read_live or get_full_board, and the opening hook about 'trading with the money rather than against it' is promotional rather than directive.

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