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

Beyond the annotations (readOnly, idempotent, open-world, non-destructive), the description discloses 'best-effort' reliability, a real failure mode (missing method error on some upstream engine versions) with a recovery path, and how to interpret empty results. That is meaningful behavioral context the annotations cannot express. It stops short of describing the shape of a successful response, though the empty-result note partially covers return semantics.

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?

Four sentences, each carrying distinct load: purpose, usage boundary, failure fallback, and result interpretation. Slightly dense in the fallback sentence, but it is front-loaded with the purpose and contains no filler.

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?

With no parameters and no output schema, the description carries the full burden and does so: it explains what the tool detects, when it applies, how it fails, and what an empty result means. An agent has everything needed to call it and interpret the outcome.

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 tool takes zero parameters, so there is no parameter meaning to add; the schema is closed and fully described. Baseline 4 applies since the description neither needs nor omits parameter guidance.

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 names a specific operation and scope: 'best-effort autodetection of tables and repeated fields on the current page.' It also implicitly separates this from siblings like importio_extract_data and importio_get_html by framing it as detection rather than extraction or raw HTML retrieval.

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?

It gives explicit when-to-use ('data pages'), when-not-to-use ('login/forms or one-off UI controls'), and a named alternative with concrete arguments ('fall back to importio_get_html with options.replaceAssets=false and selector-based inspection'). Nothing about routing is left to inference.

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