horizon_torn_getMyCompanyStock

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

No annotations are provided, and the description is a single sentence that does not disclose any behavioral traits (e.g., read-only nature, authentication requirements, caching behavior). The minimal description fails to add value beyond the tool name.

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 very concise (4 words) and front-loaded, but it sacrifices necessary detail. While brevity is positive, the extreme under-specification makes it less helpful.

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 three optional parameters, no output schema, and no annotations, the description is incomplete. It does not explain the return format, what 'stock' entails, or any prerequisites. It also fails to differentiate from numerous sibling tools.

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%, so the input schema already describes the three optional parameters (key, comment, timestamp). The description does not add any additional meaning or context for these parameters, resulting in no added value 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 'Get your company's stock' clearly indicates the tool retrieves stock data for the user's company, distinguishing it from sibling tools like 'getTornStocks' (general stocks) and 'getSpecificTornStock' (specific stock). However, it does not specify what aspect of stock is returned (e.g., price, holdings), leaving some ambiguity.

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 such as 'horizon_torn_getMyStocks' or 'horizon_torn_getCompaniesSnapshot'. There is no mention of when-not-to-use or context for selection.

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