set_city_focus

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

No annotations exist, so the description bears full responsibility. It discloses that the tool sets a focus, defines allowed values, explains the effect of 'default', and indicates it biases AI assignment. No missing behavioral traits or contradictions.

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?

Extremely concise: one-line header followed by Args list. Every sentence adds value. No fluff, directly actionable by 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?

The tool has only 2 simple parameters and an output schema (not shown). The description covers purpose and parameter semantics adequately. It does not explain return values, but output schema exists to handle that. For a straightforward setter, this is sufficient.

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 0%, so the description must compensate. It lists legal focus values and explains 'default' clears settings. For city_id, it merely says 'City ID', which is sparse but sufficient given the schema. Overall, adds significant meaning beyond 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 'Set a city's citizen yield priority.' It specifies a concrete action on a distinct resource (city yield focus), distinguishing it from sibling tools like set_city_production. No ambiguity.

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 explains that cities automatically assign citizens and this tool biases the AI toward a chosen yield. It provides context on when to use it, though it doesn't explicitly state when not to use it or list alternatives. Still, it's clear enough for an agent.

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