horizon_torn_getUserGeneric

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

With no annotations provided, the description must fully disclose behavior. However, it only states 'Get any User selection' without explaining the tool's read-only nature, output format, parameter interactions, or side effects. The complex parameter set (15 params) is left completely unexplained.

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 (one short phrase), but this brevity sacrifices clarity and utility. It fails to earn its place by providing necessary information, making it more of an under-specification than a concise statement.

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's complexity (15 params, no output schema, and many sibling tools), the description is remarkably incomplete. It doesn't explain how the tool retrieves 'any user selection' or what differentiates it from the specific user tools, leaving the agent without sufficient context to use it effectively.

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 description coverage is high (87%), so the baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions, which are themselves adequate but not enriched by the tool's description.

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 any User selection' is vague. It doesn't specify what constitutes a 'User selection' or how it differs from the many specific user tools (e.g., getUserProfile, getUserBasicInformation). The verb 'get' is too generic, and the resource is unclear, failing to distinguish the tool's purpose.

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 the numerous sibling tools that target specific user data. The agent receives no indication of prerequisites, alternatives, or context, making it difficult to select the right tool.

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