Update my country

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

The description discloses that the operation 'overwrites any previous value', which adds meaningful behavioral context beyond the annotations. It also clarifies that the value affects profile display and leaderboard filtering, giving the agent a better sense of the impact.

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 two sentences with no wasted words. It front-loads the primary action, then efficiently adds the input format and overwrite behavior.

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 simple parameter set, full schema coverage, output schema presence, and non-destructive annotations, this description is complete enough for an agent to select and invoke the tool correctly. It explains what is set, why it matters, and how the input is used.

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 the schema already documents both parameters. The description adds minor specificity by saying 'ISO 3166-1 country code', but it does not discuss the country_auto_detected parameter or provide additional parameter-level meaning.

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 uses a specific verb-resource pair ('Set the country') and clearly identifies the resource: the authenticated account's profile. It also states the purpose (country-filtered leaderboards), which differentiates it from other profile-related siblings like whoami or get_my_profile.

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 gives clear context for when this tool is appropriate: when the authenticated user needs to set or change the country shown on their profile. It does not explicitly name alternatives or exclusions, but the scope is obvious enough for a simple update operation.

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