get_wonder_advisor

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

Annotations indicate readOnlyHint=true, and the description adds detail on what the tool returns: ranked placement tiles with displacement cost, terrain, features, and resources/improvements removed. No contradiction, and behavior is fully disclosed.

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?

Five well-organized sentences: purpose, args, return description, ranking criterion, and usage tip. No wasted words, everything earns its place.

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?

Output schema exists but description still explains the returned structure. Covers ranking, terrain info, improvements removed. Could mention potential size or pagination, but sufficient for a specialized advisor tool.

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 has 0% description coverage, but the description fully explains both parameters: city_id as output from get_cities, and wonder_name with concrete examples. Adds significant meaning beyond the schema's basic titles.

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?

Description clearly states 'Show best tiles to place a wonder with displacement cost analysis.' It specifies the verb 'Show', the resource 'tiles to place a wonder', and the specific analysis type, distinguishing it from siblings like get_settle_advisor.

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?

Provides context on when to use: after calling get_cities to get city_id. Tells how to use the result: 'Use set_city_production with target_x/target_y'. Does not explicitly exclude alternatives but is clear enough.

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