aoe2_civilizations
Lists all Age of Empires II civilizations for quick reference or game planning.
Instructions
List all Age of Empires II civilizations.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Lists all Age of Empires II civilizations for quick reference or game planning.
List all Age of Empires II civilizations.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. 'List all' implies a complete, non-paginated read with no side effects, which is a useful implicit signal, but there is no disclosure of return format, whether data is cached, or how large the result set is.
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?
A single sentence with zero waste, front-loading the verb and resource immediately.
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 zero-parameter list tool this is minimally sufficient, but with no annotations and no output schema the description could reasonably hint at what each civilization record contains (name, expansion, bonuses) to help an agent decide whether to call it.
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 tool takes zero parameters, so per the rubric the baseline is 4. The description correctly implies no filtering is available, consistent with the empty input 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?
States a specific verb ('List') and resource ('Age of Empires II civilizations') with 'all' clarifying scope. However, it does not differentiate from the near-identically named sibling 'aoe2_civilization' (singular), leaving ambiguity about whether these are the same or different endpoints.
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?
No guidance on when to use this versus alternatives. The singular sibling 'aoe2_civilization' is confusingly adjacent, and the description does nothing to explain the distinction or mention the related aoe2_technologies/aoe2_units tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.