schema_explorer_preview

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

readOnlyHint=true already tells the agent this is a safe read, so the description's burden is lighter. It adds the useful fact that output is a limited 'first rows' sample, but says nothing about how the limit is enforced, whether it can be slow on large tables, or what the returned rows look like.

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 front-loaded sentence with no filler; the essential operation comes first with no preamble or redundancy.

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?

A three-parameter tool with 0% schema coverage and no output schema needs the description to explain database/table/limit semantics and the shape of returned rows. The description is silent on all three parameters, leaving an agent to guess at argument meaning and result format.

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 0%, so the description must carry the parameter burden and it largely fails. 'table or view' loosely hints at the table argument, but database and limit are never explained, and the default-50 limit is left for the agent to infer from the word 'first'.

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 phrase 'First rows of a table or view' clearly conveys the resource and the previewing operation, and 'for the Schema Explorer app' situates it. It stops short of distinguishing it from near-siblings like query_grid_rows, schema_explorer_table, or run_sql, which an agent could easily confuse it with.

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?

There is no guidance on when to use this preview versus run_sql, query_grid, or schema_explorer_table. The only hint is the app-scoping clause, which implies but does not state usage conditions or exclusions.

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