horizon_torn_getMyCompanyEmployees

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

No annotations are provided, so the description must fully disclose behavior. It only states the basic action, omitting whether the operation is read-only, what data is returned (e.g., active employees only), any pagination, or required permissions. The brief description does not compensate for missing 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 a single short sentence, which is concise but lacks necessary details. While it is efficient, it sacrifices clarity and completeness. A slightly longer description with key behavioral notes would be preferable.

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 4 parameters, no output schema, and numerous sibling tools (including 'getCompanyEmployees'), the description is incomplete. It fails to explain the return format, how the tool differs from similar ones, or any special constraints. For a tool with this complexity, more context is needed.

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 covers all 4 parameters (key, comment, striptags, timestamp) with descriptions, achieving 100% coverage. The tool description does not add any extra meaning to these parameters; baseline is 3 for high coverage, and no additional value is provided.

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 my company's employees' clearly indicates the tool retrieves employee data for the user's own company. The 'My' prefix distinguishes it from sibling 'horizon_torn_getCompanyEmployees', but it does not explicitly state that it returns a list or any other details.

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 on when to use this tool versus alternatives like 'horizon_torn_getCompanyEmployees'. No mention of prerequisites, such as being in a company, or context about authentication. The description offers no situational advice.

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