horizon_torn_getMyProperties

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 your own properties' with no disclosure of behavioral traits such as authentication needs, rate limits, pagination behavior, or what happens on error. This is insufficient for an API call.

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?

At only 4 words, the description is extremely concise but under-specified. It does not earn its place; it lacks necessary context and structure, making it inadequate for an AI agent.

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 6 parameters, no output schema, no annotations, and a large set of siblings, the description fails to provide sufficient context. It does not explain what 'properties' are, how filters work, or how to handle pagination, leaving the agent to guess.

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 already covers 67% of parameters with descriptions. The description adds no additional meaning about parameters, so it meets the baseline of 3 for high schema coverage, but does not improve understanding.

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 clearly states the verb 'Get' and the resource 'your own properties'. However, it does not distinguish this tool from the similarly named sibling 'horizon_torn_getMyProperty' (singular), leaving ambiguity about whether it returns a list or single item.

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 no mention of context, prerequisites, or exclusions, which is critical given the large number of sibling tools.

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