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

With no annotations, the description itself must indicate behavioral traits. 'Retrieve' correctly implies a read-only operation, and mentioning benchmark results adds useful context. But it does not disclose behavior on missing IDs, access constraints, or notable limitations.

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 one compact, front-loaded sentence with no filler. Every word contributes to understanding the tool's core purpose, though the section references are cryptic without added explanation.

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?

This is a simple one-parameter retrieval tool, and the output schema exists, so the description does not need to explain return values. The main gap is the absence of any usage guidance or parameter detail, but overall the definition is sufficient for correct invocation.

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% for the single parameter, and the description adds almost nothing beyond the schema's own 'Experiment Id' title. It does not explain what format the ID takes, where to find it, or any constraints.

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 uses a specific verb ('Retrieve') and a clear resource ('experiment'), and even enumerates the returned content ('details and benchmark results'). This distinguishes it from sibling tools about guidance, strategy, or experience tracking.

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?

Usage is implied: an agent would call this when experiment details or benchmark results are needed. However, there is no explicit statement of when to use it versus alternatives, nor any exclusion or prerequisite information.

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