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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is established. The description adds value by specifying exactly what the description will cover (searchable text, filters, citation practices, response limits), which gives the agent a clear expectation of the content without contradicting the annotations.

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 that front-loads the core action ('Describe the Video History Project collection') and then enumerates the key aspects covered. It is concise and avoids redundancy, though it could be slightly more structured by separating the usage hint, but it remains efficient and readable.

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 tool has no parameters and an output schema exists (which would define the return structure), the description sufficiently covers what the agent needs to know to invoke it correctly: the scope of the description (collection, searchable text, filters, citation practices, response limits) and when to use it (beginning research). No critical information is missing for this low-complexity tool.

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 tool has zero parameters, so the description has no parameter semantics to clarify. According to the baseline rule for 0-parameter tools, a score of 4 is appropriate since there is nothing to explain beyond what the schema already indicates (an empty object).

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 states the tool's purpose: to describe the Video History Project collection, including its searchable text, filters, citation practices, and response limits. This is a specific verb ('describe') applied to a distinct resource, and it differentiates itself from sibling tools like search_records or get_record, which retrieve or manipulate data rather than provide an overview.

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 provides a usage context by stating it is 'useful when beginning research,' which implies it is an entry point for orientation. However, it does not explicitly mention when not to use it or compare it to alternatives like search_records or list_terms. The guidance is present but not thorough.

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