invest_theme_date

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. '取' indicates a non-mutating retrieval, but the description discloses nothing about return format, data source, freshness, availability per date, or error behavior, which leaves an agent with only a thin behavioral picture.

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 a single sentence that packs the action, resource, and usage context without filler. It is appropriately sized and front-loaded, with the minor redundancy of '某日' vs '指定日期' being negligible.

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 one-parameter date lookup, the description gives a high-level sense of the return value and the intended dashboard use case. Yet with no output schema and no date-format guidance, an agent still has to guess about input formatting and what the result will look like, making it minimally viable but incomplete.

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%, and the description does not compensate: it only says 'specified date' without providing a format, example, or clarification for rpt_date. The parameter name is somewhat self-explanatory, but the description adds no meaning beyond what the minimal schema already makes obvious.

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 uses a specific verb '取' and a clear resource: the hot/investment-direction target portfolio for a given date. The parenthetical '看板日期切换查看' adds context, but it does not explicitly distinguish itself from sibling tools like invest_theme_latest or invest_theme_history, so differentiation is only implicit.

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 '看板日期切换查看' clause gives a concrete use case: viewing/refreshing a dashboard by switching the date. However, it does not state when not to use this tool or mention alternative tools for latest/historical theme data, so it stops short of explicit exclusionary guidance.

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