Create Simulation

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

Describes async behavior (returns immediately with simulation_id), polling mechanism with 50s blocking, and extraction of named entities. Annotations (readOnlyHint=false, openWorldHint=true) are consistent and description adds valuable context beyond them.

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?

Concise with front-loaded purpose, important warnings, and follow-up instructions. No unnecessary sentences; each part adds value.

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?

Covers all key aspects: what the tool does, prerequisites (enrich prompt, upload document), async behavior, status polling, and report availability. No gaps given complexity and schema coverage.

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 100%, but description enriches parameters: explains enrichment for prompt, the purpose of document_id, and defaults for platform. Adds clarity beyond schema fields.

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 'Run a swarm prediction' with specific components (graph build, persona generation, simulation, report). It distinguishes from sibling tools like cancel_simulation, simulation_status, and upload_document.

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?

Provides explicit instructions: enrich the prompt before calling, call upload_document first if user provides a document, and use simulation_status to poll for completion. Clearly states when to use this tool vs. others.

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