get_purchasable_tiles

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

Annotations already declare readOnlyHint=true, consistent with listing. The description adds behavioral context: it shows cost, terrain, and resources, and that tiles with luxury/strategic resources are listed first. This disclosure of ordering and content details goes beyond the annotations.

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 concise (3 sentences) and front-loaded with the core purpose. It then lists arguments, output details, and ordering. Every sentence adds value with no redundancy or waste.

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?

For a simple list tool with one parameter and an output schema (implied by context), the description covers what the tool does, its input, and what information is returned (cost, terrain, resources, ordering). This is complete for the tool's complexity.

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?

The input schema has 0% description coverage for the city_id parameter. The description adds meaningful context: 'City ID (from get_cities)', explaining the origin and type of the parameter, which compensates for the lack of schema-level documentation.

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 lists tiles a city can purchase with gold, using a specific verb 'list' and resource 'tiles a city can purchase'. It distinguishes from siblings like purchase_tile (which actually buys) and get_cities (which provides city IDs).

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 specifies the required argument (city_id) and notes it comes from get_cities, implying a prerequisite. However, it does not explicitly state when to use this tool vs alternatives (e.g., purchase_tile or other listing tools), nor does it provide when-not to use.

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