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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context by saying results are ranked by relevance and by naming the returned fields, though it omits pagination and limit behavior.

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 definition is a single front-loaded sentence with no filler. It efficiently packs purpose, result shape, and filtering into one compact statement.

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?

Because there is no output schema, it is valuable that the description names the returned fields and relevance ranking so the agent knows the result shape. The remaining gaps are around limit/pagination behavior and sibling differentiation, but the core information needed to invoke the tool is present.

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 coverage is 60%: from, to, and speaker already have schema descriptions, while query and limit do not. The description's 'Filter by date range or speaker' reinforces existing schema information but adds no semantic detail for the required query or the limit maximum.

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 ('Find') and clearly identifies the resource as 'moments in ATC shows where a subject was discussed,' then lists the returned fields. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as search_transcripts or search.

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?

The description mentions filtering by date range or speaker, but that is parameter behavior rather than guidance on when to choose this tool over alternatives. It gives no when-to-use, when-not-to-use, or sibling comparison guidance.

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