search_specific_position_by_ticker

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

No annotations provided, so description carries full burden. It only says it's an alias, but does not explain any behavioral traits (e.g., read/write, authorization needs, error behavior). The agent must infer behavior from the referenced tool.

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?

Single sentence, no redundant information. Perfectly concise for a deprecated alias. Front-loaded with the essential fact 'Deprecated alias'.

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 alias with one parameter and no output schema, the description is minimally adequate: it identifies the tool as deprecated and points to the replacement. However, it could be more helpful by summarizing what fetch_position_by_ticker does (e.g., 'returns position for ticker').

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 0% (no description for 'ticker') and the description adds no additional meaning about the parameter. The agent only knows it is a required string.

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 it is a deprecated alias for fetch_position_by_ticker(), clearly indicating its purpose as an alternative entry point to the same functionality. It distinguishes itself by pointing to the preferred sibling tool.

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?

Explicitly states this tool is deprecated and alias, directing the agent to use fetch_position_by_ticker() instead. Provides clear when-not-to-use and alternative guidance.

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