horizon_torn_getTornHonors

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

No annotations are provided, so the description must carry the full burden. It only states 'Get all honors', disclosing no behavioral traits such as read-only nature, authentication requirements, rate limits, or data format. This is insufficient for informed decision-making.

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 under-specified. It lacks any elaboration or structure, leaving the agent without meaningful context. Effective conciseness includes necessary details without redundancy.

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 has 6 parameters, no output schema, and numerous sibling tools, the description is incomplete. It does not explain the output format, pagination, or how this tool relates to similar ones like 'horizon_torn_getTornHonorsSpecific'. The agent cannot fully understand the tool's role.

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 description adds no parameter information beyond what the input schema provides. Schema coverage is 67% (4 of 6 parameters described), which is moderate but not high enough to excuse the lack of additional context. The description should clarify parameter usage, especially for generic ones like 'timestamp' and 'comment'.

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 all honors' states a specific verb and resource, making the basic intent clear. However, it does not differentiate from the sibling tool 'horizon_torn_getTornHonorsSpecific', which likely retrieves specific honors, leading to potential confusion about scope.

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. There is a sibling tool for specific honors, but no mention of when to choose 'all' versus 'specific'. The agent receives no usage context.

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