horizon_torn_getMyEvents

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

No annotations exist, so description carries full burden. Description only says 'Get your events', disclosing nothing about read-only behavior, side effects, rate limits, or caching. No behavioral traits are revealed.

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?

One-word description is extremely short but under-specified. It lacks structure and fails to convey necessary information. Not concise; it's incomplete.

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?

Tool has 7 parameters and no output schema. Description provides no information about return values, filtering logic, or how to use parameters. Completely inadequate for effective usage.

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 86%, high, so baseline is 3. The description adds no parameter information beyond what the schema already provides. No additional meaning or context is given for the parameters.

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 is 'Get your events' which is vague. It names a verb and resource but doesn't specify what 'your events' refers to (e.g., personal logs, calendar events, game notifications). Among many sibling tools with 'My' prefix (e.g., getMyAttacks, getMyMessages), it doesn't differentiate itself.

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 vs alternatives. No context about prerequisites or limitations. The description provides no usage instructions.

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