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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. Beyond that, the description usefully discloses the shape of the response (titles, URLs, dates, lead finding, and a pointer to a deeper brief), which annotations and the schema do not provide — especially valuable since there is no output schema.

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?

Two sentences with zero filler; the search scope is front-loaded and the return summary follows. Nothing is repeated from the schema or annotations.

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 three-parameter, non-destructive read tool with a fully documented schema, the description covers scope and return contents, which is what an agent needs to call it. It falls short of complete only in not situating the tool against the other research/brief tools in the sibling set.

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 description coverage is 100%, so the schema already documents query, kind (with an enum) and limit with its 1–10 bound. The description adds only the loose notion of "keywords" and implies a brief may be returned, but does not explain the kind filter options or what limit controls. Baseline 3 is appropriate.

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 gives a specific verb and resource ("Search the free CULT+MATH studies and answers (and the briefs) by keywords") and lists what comes back (titles, URLs, dates, lead finding, brief). It is clearly distinct from get_document or list_decision_briefs by virtue of being a keyword search, though it does not name those siblings explicitly.

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 intent to keyword-search the corpus is implied, but there is no explicit statement of when to reach for this tool rather than get_decision_brief, get_document, or list_decision_briefs. No exclusions or prerequisites are given, so the agent must infer routing from the sibling names.

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