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

No annotations are present, so the description carries the full burden. It reveals what the simulation models—social dilemmas, speech acts, and reputation—but does not disclose whether the simulation has side effects, whether state persists, what is returned, or whether it is safe/non-destructive. 'Simulate' hints at computation, but this remains implicit.

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 a single front-loaded sentence with no filler. Every phrase—'repeated multi-agent interaction,' 'social dilemmas,' 'speech acts,' 'reputation tracking'—adds meaningful information, making it efficient and well structured.

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 tool with four parameters, zero schema descriptions, and no annotations, one sentence is insufficient. The output schema helps clarify return values, but an agent still lacks guidance on parameter values, optional behavior, and how this tool relates to simulation siblings. Significant context 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?

Schema description coverage is 0%, and the description does not explain game_type, num_rounds, agent_actions, or opponent_policy. Parameter names and defaults give partial clues, but agent_actions is opaque and no valid options are described, so the description fails to compensate for the missing 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 uses a specific verb plus resource: 'Simulate repeated multi-agent interaction' and lists distinctive features—social dilemmas, speech acts, and reputation tracking. These features help separate it from sibling tools like simulate_actions or create_simulated_environment, making its purpose easy to grasp.

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?

Usage is only implied: an agent can infer this tool is for repeated multi-agent simulations, but the description does not explicitly state when to choose it over alternatives such as cognitive.simulate_actions or cognitive.run_closed_loop_agent. No exclusions or when-not-to-use guidance is provided.

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