send_envoy

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action and prerequisite but does not describe side effects (e.g., consumption of envoy tokens), irreversibility, required game phase, or what the tool returns despite the presence of an output schema.

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 three short sentences with the core action first, followed by parameter definition and prerequisite. Every sentence adds value without redundancy, making it highly efficient.

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 tool with one parameter and an output schema, the description covers the main purpose, parameter source, and a key prerequisite. It does not describe the return value, but the output schema likely provides that. Overall, it is mostly complete for the agent's needs.

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 coverage is 0% (no description in schema), but the description adds meaning by explaining the player_id parameter as 'The city-state's player ID (from get_city_states),' sourcing it from a sibling tool. This compensates well for the lack of schema 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 starts with 'Send an envoy to a city-state,' which is a specific verb-resource-target combination. It clearly distinguishes from sibling tools like 'send_diplomatic_action' or 'form_alliance' by focusing on envoys and city-states.

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?

It states the prerequisite 'Requires available envoy tokens' and directs the agent to 'Use get_city_states to see options,' providing clear guidance on when and how to use the tool. It does not explicitly mention when not to use, but the requirement and reference to sibling tool are helpful.

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