horizon_torn_getTornBounties

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

No annotations and the description provides no behavioral details. It does not mention whether it's read-only, requires authentication, or any side effects, leaving the agent uninformed.

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?

Three-word phrase is under-specified, not conciseness. It lacks necessary detail, making it inefficient for the agent to infer correct usage.

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?

With 5 parameters, no output schema, and many sibling tools, the description is severely incomplete. No mention of pagination, filtering, or response structure.

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 only 60% (some parameters have descriptions), but the tool description adds no extra meaning. It fails to explain the purpose of limit, offset, or timestamp parameters beyond what the schema provides.

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?

Description 'Get bounties' is vague, essentially a tautology of the tool name. It does not specify whether these are global, user-specific, or faction bounties, and fails to distinguish from siblings like horizon_torn_getMyBounties or horizon_torn_getUserBounties.

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 guidelines on when to use this tool vs. alternatives. Given numerous sibling tools with similar names, explicit context for usage is missing.

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