horizon_torn_getMyReports

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

No annotations are present, and the description provides no behavioral context. It does not disclose whether this is a read-only operation, if it returns paginated results, any rate limits, or side effects. With 8 parameters, the behavior is unclear.

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 (3 words), which is efficient in length but sacrifices necessary detail. It is front-loaded but insufficient for a tool with 8 parameters.

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?

The description is severely incomplete given the complexity (8 parameters, no output schema, no annotations). It fails to explain what reports are returned, how filtering works, or any return format. The tool name implies it returns personal reports, but no context is provided.

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 75%, so the baseline is 3. The description adds no parameter information beyond what the schema already provides. It does not clarify how parameters like 'cat', 'sort', 'limit', or 'target' affect results.

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 your reports' is minimal and tautological. It states the resource is reports but does not differentiate from many sibling tools like horizon_torn_getMyFactionReports or horizon_torn_getMyFactionLatestChainReport. The verb 'Get' is generic and lacks specificity about what kind of reports (e.g., personal, faction, chain).

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. The description provides no context about prerequisites, when to prefer this over other report-related tools, or any exclusions.

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