invariance_list_runs

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

With no annotations, the description carries the full burden of explaining behavior, but it discloses none. It only identifies the tool as an alias and does not mention list semantics, read-only behavior, return format, pagination, or error conditions.

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 extremely short and has no filler, but it is too sparse to be useful. Under-specification is not conciseness, and the single sentence provides only a reference to another tool rather than meaningful self-contained content.

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?

Although the tool is simple with zero parameters, the description is incomplete in context. It relies entirely on the reader knowing invariance_run_list, but sibling descriptions are not provided, and the actual listing behavior and return characteristics are absent.

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?

The tool has zero parameters and an empty input schema, so there is nothing for the description to explain. Per the baseline for zero-parameter tools, the description does not need to compensate for missing parameter 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 does not state what the tool does; it merely points to another tool as an alias. An agent must already know what invariance_run_list does in order to understand this tool, and the description is essentially a cross-reference rather than a self-contained purpose.

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?

No when-to-use guidance is provided. The word 'alias' implies interchangeability with invariance_run_list, but there is no explanation of when to choose this alias over the canonical tool, and no mention of alternatives or exclusions.

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