fetch_open_position_by_ticker

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

No annotations are provided, so the description carries the full burden. It discloses the tool is deprecated and an alias, which is helpful, but does not describe any behavioral traits like side effects, authorization needs, or what happens when called. It meets the minimum for a deprecated alias but lacks depth.

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 extremely concise with no extraneous words. It is front-loaded with the key information (deprecated alias) and immediately provides the alternative. Every word earns its place.

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?

Given the tool is a deprecated alias with one parameter and no output schema, the description adequately conveys the essential information: it is deprecated and redirects to another tool. However, it lacks details about the parameter and the behavior of the underlying tool, which could be helpful for completeness.

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 one parameter (ticker) with no description, and schema description coverage is 0%. The description adds no meaning beyond the parameter name, leaving the agent with no guidance on what the ticker should be or how it affects behavior.

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 it is a deprecated alias for fetch_position_by_ticker(), so the agent knows the tool's purpose is to redirect to another tool. However, it does not explain what fetch_position_by_ticker does, so the purpose is clear only in the context of the alias.

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 explicitly says 'Deprecated alias' and names the alternative tool (fetch_position_by_ticker). This tells the agent not to use this tool and suggests the correct one, providing excellent usage guidance.

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