horizon_torn_getMyBasicInformation

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states the purpose without mentioning read-only nature, authentication requirements, rate limits, or any side effects. The single sentence is insufficient for transparency.

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 sentence with no wasted words. While concise, it could be slightly expanded to include key behavioral or usage details without harming structure. Currently efficient but minimally informative.

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 tool has 4 optional parameters, no output schema, and no annotations. The description offers no hint about the return format or fields included in 'basic profile information'. In the absence of an output schema, the description should provide at least a general idea of what data is returned.

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% coverage for all 4 parameters with individual descriptions. The tool description does not add any additional meaning beyond what the schema already provides. Per rules, baseline 3 is appropriate as the schema does the heavy lifting.

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 basic profile information' clearly states the action (get) and the resource (basic profile information). It distinguishes this tool from other 'getMy...' tools by specifying 'basic' rather than full profile, but it does not explicitly differentiate from 'horizon_torn_getMyProfile' which may return similar data.

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 versus alternatives like 'horizon_torn_getMyProfile' or other user-specific tools. The description lacks context on when 'basic' information is sufficient or what distinguishes it from other profile endpoints.

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