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

With no annotations, the description carries the full burden. It discloses safety and predictability: 'These runs never execute AI-generated code or parameters' and are 'deterministic allowlisted.' It also clarifies they are 'not physical measurements or independent reproductions.' This is rich behavioral context for a read operation.

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 with no wasted words. The primary purpose is front-loaded, and the clarifying constraints follow immediately. Every sentence adds value without repetition.

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 read-only tool with one optional parameter and no output schema, the description is largely complete. It states what is returned (runs and boundaries), what the tool does not do (execute code, physical measurements), and its deterministic nature. Missing details like pagination or limit semantics are minor for a simple list operation, so it is adequate.

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%, so the description should explain the 'limit' parameter. It does not mention it at all. While the parameter is simple (an optional integer), the description provides no guidance on how limit affects results or its default behavior. Since the parameter is not documented in the description, the agent may not know how to use it effectively.

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 states a clear verb ('Read') and resource ('deterministic allowlisted simulation runs and their plain-English boundaries'). It distinguishes itself by noting these runs 'never execute AI-generated code or parameters' and are 'not physical measurements or independent reproductions,' which helps differentiate from siblings like commons_list_hosted_runs or research_cycles. However, it does not explicitly name an alternative tool, so it is strong but not a 5.

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 when to use the tool by describing the type of runs it reads (deterministic, allowlisted) and what it excludes (not physical measurements or reproductions). It gives contextual guidance but does not explicitly state 'use this when...' or mention any sibling tool by name. There is no clear when-not-to-use guidance, but the constraints are inferable.

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