simulation_models

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

With no annotations, the description carries full burden. It discloses that live execution is opt-in and that unavailable providers fall back to deterministic clean-room simulation, which is critical behavioral context beyond a simple list. No contradictions.

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?

Two sentences, no wasted words. The first sentence immediately states the main purpose, and the second adds key behavioral nuance. Perfectly front-loaded and concise.

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 list tool with no parameters and no output schema, the description provides sufficient context about what is listed and the behavioral nuance. However, it doesn't describe what fields the list contains, which would enhance completeness slightly.

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?

There are zero parameters, so schema coverage is 100% by virtue of emptiness. The description adds meaning by specifying the scope ('Codex-first model profiles for Memoire simulations') and fallback behavior, providing value beyond the empty 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 the tool lists 'Codex-first model profiles available to Memoire model-swarm simulations', with a specific verb ('list') and resource ('model profiles'). It distinguishes from sibling tools like simulation_run by focusing on listing available models.

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 implies usage for listing models before simulations, but does not explicitly state when to use this tool versus alternatives (e.g., simulation_list_runs). It lacks exclusions or alternative suggestions, leaving the agent to infer context.

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