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

With no annotations, the description carries the full burden. 'Retrieve' signals a read-only operation, but the description discloses no additional behavioral context such as auth requirements, side-effect guarantees, or error/rate-limit behavior. The section references are 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 front-loaded sentence with no redundant wording. It loses a point for the cryptic '(§24, §69)' suffix, which is likely noise for an AI agent, and for lacking any structuring of usage context.

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 simple one-parameter read tool with an output schema, the description is nearly sufficient: an agent can infer it needs an experiment_id and will receive details/results. However, the absence of usage guidance, parameter provenance, and differentiation from the dot-form sibling leaves selection and invocation partly to 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 provides only a `string` experiment_id with 0% description coverage, and the description never mentions the parameter or how to obtain/format it. The word 'experiment' maps loosely to experiment_id, but no semantic value is added beyond the property name.

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') with a clear resource ('an experiment') and specifies the content ('details and benchmark results'). It is not a tautology, but it does not differentiate from the near-identical sibling `cognitive.get_experiment`, and the § references add no clarifying value.

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 explicit guidance on when to choose this tool over the many get_* siblings, nor any exclusions or prerequisites. The only usage signal is the implied 'when you need experiment details', which is not enough to distinguish it from the duplicate dot-form sibling.

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