aibench_compare

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Compare...' with no mention of whether this is read-only, what output it produces, whether it requires prior benchmark runs, or how it behaves if inputs are invalid. The description does not contradict annotations because there are none, but it leaves the tool's behavior largely opaque.

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 a single sentence with no filler, which is concise. However, it is underspecified and grammatically unclear, so the brevity is not an asset: it lacks enough structure to convey the intended meaning precisely.

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 the sibling tools and the absence of an output schema, the description should clarify what the comparison returns, how left and right identify benchmark items, and what conditions must hold for a valid comparison. None of that is present, so the description is not complete enough for an agent to call the tool correctly without additional inference.

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 schema has 100% description coverage, but the parameter descriptions are minimal ('Left' and 'Right') and add no real semantics. The tool description adds a small amount of meaning by implying left and right are the two items to compare, but it does not explain their expected format, whether they are identifiers, names, or paths. Baseline 3 is appropriate because the schema covers parameter names, even though the descriptions are thin.

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 the verb 'Compare' and a resource ('standardized model benchmarks items'), which gives a general sense of the tool. However, the phrase 'two run standardized model benchmarks items' is grammatically awkward and vague, and it doesn't specify what aspect is compared or what the result is. It is distinguishable from siblings only at a coarse level: compare vs. list/status/inspect.

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 about when to use this tool versus aibench_status, aibench_list, or aibench_inspect. No mention of alternatives, prerequisites, or exclusions is present. The only implied usage is 'use this when you need to compare two items,' which is too thin to route an agent reliably.

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