fund_linghuo_position_lg

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, which fully cover the safety profile. The description adds the return type (pandas.DataFrame) and the data source URL, but no additional behavioral traits such as update frequency or historical coverage.

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 and includes key details (title, URL, return type, data source). It is structured but lacks a substantive summary of what the data represents. It is not overly verbose, but the content is somewhat minimal and boilerplate.

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 parameters and no output schema, the description carries the burden of explaining the return value. It states the return type (pandas.DataFrame) but does not describe the structure, columns, or time range. Given the tool's simplicity, this is adequate but not complete.

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?

The tool has zero parameters, so there is no parameter semantics to explain. Schema coverage is 100% (empty properties), making the schema fully sufficient. The description's mention of the return type adds useful context beyond the schema.

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 identifies the resource (fund positions for flexible allocation funds) and the data source (乐咕乐股 with a specific URL). The verb is implied as retrieval. It distinguishes from siblings like fund_balance_position_lg and fund_stock_position_lg, which target different fund categories.

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 explicit guidance on when to use this tool compared to other fund position tools. It does not state when this tool is preferred or mention any exclusions. The description only provides a data source and return type.

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