aoe2_civilization

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it is implied to be a read, but there is no statement about error behavior for unknown IDs, whether the ID is numeric or slug-like, or what data comes back. For a zero-annotation tool this is a meaningful gap.

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 short sentence with the verb and resource front-loaded and no filler. It is efficient, though it borders on under-specification rather than being richly concise.

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?

With one fully documented parameter, no nested objects, and no output schema, the definition is minimally adequate for a simple lookup. It stops at the minimum, providing no return-shape or error context that an agent could use, but nothing essential is missing.

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?

There is exactly one parameter with 100% schema description coverage, so the schema already defines 'id' as a Civilization ID. The description's 'by ID' adds no format, range, or valid-value detail beyond that, so the baseline 3 applies.

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 states a clear verb ('Get') and resource ('Age of Empires II civilization') scoped by ID, which is unambiguous on its own. However, it does not distinguish this single-entity lookup from the sibling aoe2_civilizations (plural), which an agent must infer is the list variant.

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?

There is no guidance on when to use this tool versus aoe2_civilizations or aoe2_unit/aoe2_units. The 'by ID' phrasing hints at the lookup pattern, but no alternatives or conditions are stated.

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