horizon_torn_getRacingRaceDetails

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Get specific race details', omitting any traits like auth requirements, error behavior, or data scope (e.g., does it return all fields?). This is insufficient for a mutation-less read tool.

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 short (one phrase), which could be considered concise, but it under-specifies the tool. It lacks structure and fails to earn its place by providing necessary context. More detail is needed for this tool to be 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 the tool has 4 parameters, no output schema, and a large set of sibling tools, the description is incomplete. It does not explain what 'race details' entails, nor does it provide any context about return values or usage patterns. The agent would be underinformed.

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 has 100% description coverage for all 4 parameters. The descriptions are functional but minimal (e.g., 'Race id', 'API key (Public).'). The tool description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 specific race details' clearly states the verb and resource, but it does not differentiate this tool from siblings like horizon_torn_getRacingRaces, which also retrieves race data. The description is adequate but lacks distinctiveness among many racing-related tools.

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 vs alternatives. It does not mention prerequisites, scenarios, or exclusions, leaving the agent with no context for selection.

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