send_diplomatic_action

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

No annotations provided; the description covers cost and rejection for delegations and mentions tech requirements, but omits rate limits, cooldowns, or success/failure effects.

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 well-structured with a clear list of actions and supporting details, though the action enumeration could be slightly more compact without losing clarity.

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?

Given the output schema exists, return values are covered; however, the description omits some war type conditions (e.g., liberation war) and does not specify behavior for invalid inputs.

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?

With 0% schema coverage, the description fully explains both parameters: other_player_id is from get_diplomacy output, and action lists all valid values, adding essential meaning beyond the minimal 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?

The description clearly states 'Send a proactive diplomatic action to another civilization' with a comprehensive list of actions, distinguishing it from sibling tools like respond_to_diplomacy.

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 advises using get_diplomacy to see available actions and notes prerequisites for some actions, but does not explicitly guide when to choose this tool over alternatives like form_alliance.

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