Resolve Steam Vanity URL

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

No annotations are provided, so the description bears the full burden. It only states what the tool does, not how it behaves. For instance, it does not disclose that this is a potentially read-only operation, whether authentication is required, or if there are rate limits. The description is too terse to convey behavioral traits.

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 fluff, achieving conciseness. However, it could be slightly expanded to improve completeness without losing conciseness.

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 is simple (one parameter, output schema exists), the minimal description is borderline sufficient. It explains the core transformation from vanity name to SteamID64, which is the primary purpose. However, it does not explain the output format or any edge cases, making it slightly incomplete.

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?

With 0% schema description coverage, the description should add context for the parameter. It does not elaborate on what a 'vanity URL name' is (e.g., custom URL, not full URL). The parameter name is self-explanatory, but the description adds no extra meaning beyond the schema.

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 tool's core function: resolving a Steam vanity URL to a SteamID64. The verb 'resolve' and the resource 'Steam vanity URL name' are specific, and it is distinct from sibling tools like 'steam_get_profile' or 'steam_search_library'.

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. There is no mention of prerequisites, typical scenarios, or when not to use it. For example, it does not explain that this is a prerequisite for getting a user's profile or other user-specific data.

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