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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing behavioral on top: no mention of match semantics (substring vs fuzzy), result ordering, result limits, pagination, or the fact that hits can span three entity types with different shapes.

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?

A single front-loaded sentence with zero filler; the verb and the searchable resource set lead. It is efficient, though the extreme brevity is part of why the usage and parameter detail are absent rather than a virtue on its own.

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 search entry point with no output schema, the description should at minimum indicate what comes back (mixed study/build/release results) and any result limits or pagination. None of that is present, so an agent cannot predict the response shape before calling.

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?

There is one parameter with 0% schema description coverage, so the schema documents nothing about 'query' beyond type, minLength 1 and maxLength 120. 'By keyword' hints at the intended input but does not explain tokenization, quoting, multi-word handling, or the 120-character cap, leaving the parameter substantially undocumented.

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?

States a specific verb ('Find') and resource set ('studies, builds and releases') scoped by keyword, which lets an agent distinguish it from the type-specific siblings like get_build or list_studies. The multi-entity cross-search scope is clear, though the description never explicitly contrasts itself with those single-entity sibling tools.

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 phrase 'by keyword' implies this is the tool to reach for when doing free-text lookup rather than ID-based retrieval, but the description gives no explicit when-to-use, when-not-to-use, or named alternatives among the seven siblings. Usage is inferred rather than stated.

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