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

With no annotations, the description bears the full burden. It reveals case-insensitivity and a limit of 50, but omits behavior for empty results, default values, or error handling. Adequate but not exhaustive.

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, tightly worded with no redundant content. It directly conveys the essential behavior and constraints.

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 simple search tool, the description is sufficient. It specifies the search scope, matching behavior, and result limit. No output schema exists, but the tool's purpose is clear enough without detailing return structure.

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 description adds meaning to query (case-insensitive) and limit (up to 50) beyond the schema's constraints. Query's schema description is minimal, but the description clarifies semantics. Limit has no description but the description supplies its practical meaning.

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 that the tool returns rows containing the query, distinguishing it from sibling tools like dataset_stats or dataset_columns. The verb 'search' is implicit but the function is unambiguous.

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 implies when to use (searching content), but does not explicitly mention alternatives or when-not-to-use. Sibling names suggest distinct purposes, yet no direct comparison is given.

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