operate

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

Annotations declare readOnlyHint=true, and the description adds details: peek uses DuckDB SUMMARIZE, reads whole file, honors source-size ceiling; sql is read-only using view 'data'; failures documented. No contradiction.

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 informative but slightly verbose; each sentence adds value but could be tightened. Front-loaded with purpose, then operations, then prerequisites.

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 tool with 5 operations, 6 parameters, and no output schema, the description adequately covers all ops, parameter usage, prerequisites, failure modes, and links to other tools (resolve). Indirectly describes return types.

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 covers 5/6 params (83%) with descriptions; the description adds meaning by explaining each op value, file addressing by catalog id + file name, default n=20, and sql view 'data'. Adds significant value beyond schema.

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 it inspects/queries remote tabular files without downloading, lists five specific operations (schema, preview, head, sql, peek), and distinguishes from siblings like fetch (download) and resolve (ID lookup).

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 explicitly says when to use (inspect/query without download), prerequisites (resolve id first, need [operate] extra), failure conditions (fails if not operable), and hints at alternatives via sibling context.

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