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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses case-insensitivity and the limit cap, but does not mention whether the operation is read-only, any side effects, return format details, or pagination behavior. Adequate but minimal for a search tool.

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 sentence with no waste, front-loading the core behavior and constraints. Every word contributes to the agent's understanding.

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?

There is no output schema, so the description must specify what is returned. It says 'Rows of the HardscapeDesk dataset' which implies the output, but it does not clarify whether full rows are returned, how results are ordered, or if any other metadata is included. For a search tool this is a moderate gap.

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 50%: the query parameter has a description ('text to look for in any cell'), while limit lacks a description but has min/max constraints. The description adds case-insensitive behavior, which is not in the schema, but does not explain limit beyond the schema's maximum. 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 states a specific verb ('search'), a specific resource ('HardscapeDesk dataset'), and precise criteria (cells containing query, case-insensitive, up to 50). It clearly distinguishes this from sibling tools like dataset_stats or dataset_row, which have different purposes.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions. Usage is implied by its search functionality, but no explicit guidance or comparison with siblings is provided, leaving the agent to infer context.

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