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

The description adds critical context beyond the annotations and schema by defining the scope of the data ('Real Alpha cut'), the sorting behavior ('newest first'), and what supplementary metadata will be provided ('who they are and links their page').

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 highly information dense, packing scope, ordering, filtering logic, and output context into a single sentence without becoming confusing or overly wordy.

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 high coverage of the input schema and strong read-only annotations, the description fully conveys all necessary operational constraints (scope, ordering, retrieval method) for the agent to use the tool correctly and confidently.

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?

While the schema is comprehensive, the description adds semantic weight by specifying that the `topic` parameter can be 'a topic or a few words' and reinforces the default behavior for the `limit` parameter (10 if not given). This adds necessary interpretive value.

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 clearly defines the tool's function as retrieving specific statements or 'moments' from interviews within the 'Real Alpha cut.' It is highly specific and immediately identifies the data source.

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?

It provides clear usage guidance by explaining the result ordering ('newest first') and the matching criteria ('every moment where they are talking, or only those on a topic, best match first'). This helps the agent contextualize when and how the data will be retrieved.

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