Jobs

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

With no annotations, the description carries the full burden but discloses almost nothing: it doesn't say that 'clear' destroys queued jobs, that 'run' executes work (possibly in parallel), whether solver_type filters or selects, or what permissions or side effects apply. For a tool with destructive and execution actions, this is a significant gap.

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 single sentence is front-loaded and free of waste, which is good structure. It is under-specified rather than bloated, so it loses a point for not earning its place with any actionable detail.

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?

Given four parameters, a multi-action enum with destructive/execution semantics, no annotations, and only a one-line description, the definition is not complete enough for an agent to invoke it confidently. An output schema exists, so return values needn't be explained, but the behavioral gaps around clear/run remain.

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 100%, so each parameter (action enum, file_path, solver_type, parallel_mode) is already documented in the schema. The description adds no meaning beyond that, so the baseline of 3 is appropriate rather than higher.

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?

"Manage the simulation job queue" gives a verb and resource, but "manage" is vague and hides the four distinct operations (add/list/clear/run) that the schema reveals. It does not distinguish this tool from siblings like run_action or add, which could plausibly overlap with queue actions.

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?

There is no guidance on when to use this tool versus run_action, add, or the other job-related siblings, nor when each action is appropriate. The agent must infer from the enum that 'add' enqueues and 'run' executes, and nothing says which context selects this over a sibling.

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