steam_clearAchievement

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

No annotations are provided, so the description must convey behavioral traits itself. It discloses that the call is via the partner API and requires specific authentication, but it does not mention error handling, idempotency, or lack of side effects beyond clearing the achievement. Given the simple action, this is adequate but not comprehensive.

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: two sentences that immediately convey the purpose, intended use, and a key prerequisite. Every phrase adds value without redundancy.

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?

There is no output schema. The description does not explain what the tool returns on success or failure, nor does it cover potential error conditions. While the tool is simple, the lack of return information leaves a gap in understanding the full behavior.

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 100%, so baseline is 3. The description adds extra context to the 'achievement' parameter: 'e.g. ACH_BEAT_LEVEL_1. Must match a name configured in Steamworks.' This provides valuable guidance beyond the schema's minLength and type. The other parameters are also well-described in 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 verb 'clear' and the resource 'achievement', and explicitly says 're-lock' which distinguishes it from the sibling tool steam_setAchievement (which typically unlocks). This provides specific purpose differentiation.

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 context by specifying 'Intended for dev/test use' and lists a clear prerequisite: 'Requires a publisher API key with server IP allowlisted in Steamworks partner settings.' It does not explicitly mention when not to use or alternative tools, but the dev/test restriction guides appropriate usage.

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