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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about this being a mutating game action — no resource cost, no state effects, no idempotency behavior despite idempotency_key being a parameter, and no error/rate-limit context. The single sentence adds no behavioral information beyond the name.

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?

It is brief, but brevity here is under-specification rather than conciseness — the one sentence is a name restatement plus an API mapping that gives an agent nothing actionable.

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 mutating, unannotated game action with two undocumented parameters, no output schema, and 33 competing siblings, the description omits everything an agent would need: what the action consumes or produces, and when it is the right choice.

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% and the description documents neither parameter. city_id (required) and idempotency_key have no format, valid-value, or semantic explanation anywhere, which is a serious gap for an action that presumably targets a specific city and supports safe retries.

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 only restates the tool name and equates it with an HTTP endpoint ("identical to POST /api/contribute_stockpile"). It never says what contributing a stockpile actually does in Agent City Wars terms, nor how it differs from the many other action siblings such as build, research, or trade_offer.

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 call this action, what prerequisites exist, or which sibling action to prefer instead. The endpoint equivalence gives no help in choosing between contribute_stockpile and the 30+ other game actions.

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