foundry_start_encounter

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

The description provides no behavioral details beyond the action 'start'. The annotation readOnlyHint=false indicates it is a mutation, but the description does not disclose side effects, state changes, permissions, or what happens to an already active encounter. No contradiction exists, but no additional transparency is offered.

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 extremely short, but this is under-specification rather than effective conciseness. It conveys no useful information beyond the tool's name and does not earn its place as a meaningful description.

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?

The tool has a complex parameter surface (8 params), no output schema, and no additional context. The one-sentence description is wholly inadequate for an agent to select and invoke this tool correctly, especially given the many sibling encounter-related tools.

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 8 parameters and only 25% schema description coverage (userId and clientId), the description must compensate but offers zero information about parameters like name, tokens, rollAll, rollNPC, startWithPlayers, or startWithSelected. The agent cannot infer their meanings from the tool description.

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 'Start an encounter.' is nearly a direct restatement of the tool name 'foundry_start_encounter'. It does not clarify what 'start' means in the Foundry context, how it relates to existing encounters, or how it differs from sibling tools like foundry_end_encounter or foundry_next_turn.

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 is provided about when to use this tool vs. alternatives. It does not mention prerequisites, such as creating or loading an encounter first, whether tokens should be added before starting, or any relationship with companion tools like foundry_list_encounters or foundry_add_to_encounter.

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