fund_stock_position_lg

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the data source URL and return type (pandas.DataFrame) but does not disclose additional behavioral traits such as data update frequency, columns included, or any rate limits. It provides minimal added value beyond the annotations.

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 brief and avoids unnecessary fluff, consisting of a title, source URL, and return type. However, the structure is fragmented with ':return:' and ':rtype:' lines, and there is slight redundancy between the title and the return description. It is appropriately sized but could be more polished.

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 zero-parameter tool with no output schema, the description should clarify what the returned DataFrame contains. It only states 'stock fund position' without specifying columns, time range, or units. This leaves the user guessing about the data structure, though the source URL allows further investigation. It is minimally complete but lacks useful context.

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 input schema has zero parameters, so the description has no parameter semantics to explain. Per guidelines, the baseline for zero-parameter tools is 4, and the description correctly omits parameter details since none exist.

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 identifies the tool as retrieving stock fund position data from Legulegu (乐咕乐股) with a specific source URL, which distinguishes it from sibling fund position tools like fund_balance_position_lg and fund_linghuo_position_lg. However, it lacks an explicit verb like 'get' or 'fetch', relying on the tool name to convey the action.

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 no guidance on when to use this tool versus alternatives. It does not mention that this is specifically for stock-type funds, nor does it contrast with other fund position tools. There are no usage criteria, exclusions, or alternative tools suggested.

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