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

With no annotations provided, the description carries the full burden. It discloses key behaviors: case-insensitive matching, cell containment, and a maximum of 50 rows. However, it does not mention potential side effects (none expected), error conditions, or the return format. This is adequate but minimal.

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, concise sentence that front-loads the core purpose and constraints. There is no wasted text; every part is informative.

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 with two parameters and no output schema, the description covers the essential behavior: what it searches, how it matches, and the limit. It lacks explicit mention of return structure or empty-result behavior, but these are not critical for a basic search. It is sufficiently complete for an agent to call it correctly.

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% (query has a description, limit does not). The description adds value by clarifying that the query is matched case-insensitively and that the result is limited to 50 rows, which helps interpret the 'limit' parameter beyond its min/max. However, it does not elaborate on the limit parameter's name or behavior in detail.

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 the tool's purpose: returning rows from the Topcoatly dataset where cells contain the query. It specifies the verb (search/return), resource (dataset), and conditions (case-insensitive, limit). It is distinguishable from siblings like dataset_stats or dataset_columns, which serve 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 implies usage for finding rows matching a text query, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. The context is clear from the name and description, but no direct guidance is given.

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