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

No annotations are present, so the description carries the behavioral disclosure burden. It discloses the matching scope (any cell), case-insensitive behavior, and the 50-row limit, which are useful traits beyond the schema. It does not specify ordering or the default limit when omitted, but the core behavior is adequately transparent.

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, well-structured sentence with no wasted words. It front-loads the key facts: dataset, matching behavior, case-insensitivity, and result cap.

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 two-parameter search tool, the description covers the essential behavior and result scope. However, there is no output schema and no annotation, so details like return row structure, default limit, ordering, and relationship to sibling tools are left unstated.

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 schema documents query as 'text to look for in any cell,' and the description adds case-insensitive matching, which is helpful. The limit parameter has no schema description, and the description's 'up to 50' partially compensates but does not clarify the default behavior or the exact role of the limit parameter beyond the schema maximum.

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 what the tool returns: rows of OrderPadLedger whose cells contain the query, and it adds case-insensitivity and a 50-row cap. It is distinct from siblings like dataset_row or dataset_columns, but it does not explicitly call out how it differs from them.

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?

No explicit guidance is given about when to use this search tool versus alternatives such as dataset_row or dataset_stats. The intended use is implied from the word 'search,' but there are no when-to-use or when-not-to-use instructions.

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