horizon_torn_getMyStocks

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get your stocks', omitting details about authentication requirements, side effects, response format, or data scope (e.g., current holdings or transaction history).

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 at four words, but it is under-specified. While conciseness is good, a sentence or two more about the resource being retrieved would improve clarity without becoming verbose.

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 absence of an output schema and limited description, the agent lacks context about what data is returned (e.g., stock names, quantities, prices). The tool is simple, but more detail (e.g., 'Returns your current stock portfolio with quantities and purchase prices') would be helpful.

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 100% – all three parameters (key, comment, timestamp) are described in the schema. The description adds no additional meaning beyond what the schema provides, which is acceptable since the parameters are standard across many tools.

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 'Get your stocks' clearly indicates the tool retrieves the user's own stock holdings. However, it does not explicitly differentiate from sibling tools like 'horizon_torn_getTornStocks' (all TORN stocks) or 'horizon_torn_getSpecificTornStock', relying on the 'My' naming convention, which is adequate but could be more explicit.

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 guidance is provided on when to use this tool versus alternatives. For example, it does not state that it returns only the user's portfolio as opposed to market-wide stock data, nor does it mention any prerequisites or limitations.

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