get_dc_index

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

No annotations provided, and the description only implies read-only via '获取' (get). It does not disclose safety, side effects, rate limits, or any behavioral constraints beyond a basic retrieval operation.

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 efficient sentences: first states main purpose, second lists key data fields. No redundancy, front-loaded, and every word contributes value.

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?

The description provides basic context about retrieved fields but omits parameter relationships (e.g., how ts_code and name interact). With no output schema, some additional parameter usage hints would improve completeness for this 5-parameter tool.

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?

Input schema covers all 5 parameters with full descriptions. The description adds no extra meaning beyond the schema; it only summarizes returned data types. Baseline 3 is appropriate given full schema coverage.

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 retrieves East Money concept sector information and lists included data types (rise/fall, leading stocks, market cap, turnover). This distinguishes it from sibling tools like get_ths_index (THS index) and get_dc_daily (daily data).

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 on when to use this vs. siblings such as get_dc_daily or get_dc_member. The description focuses on what the tool does without context about filter combinations or appropriate use cases.

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