cbs_estimate_dataset_size

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

Annotations cover readOnly, destructive, idempotent, openWorld hints fully. Description adds output details (row count, column count, fetch strategy), which is useful context beyond annotations.

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?

Short and to the point. The 'Args:' and 'Returns:' formatting is slightly verbose but still concise overall. No unnecessary words.

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?

Given one parameter, full schema coverage, and existing output schema, the description fully covers what an agent needs. No missing details.

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 100%, description essentially repeats schema with minor restructuring. Adds some clarity on nested object but no novel meaning beyond schema descriptions.

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 estimates dataset size before fetching, with a specific verb and resource. This distinguishes it from siblings like cbs_check_dataset_availability or cbs_get_metadata.

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?

Implied usage from 'before fetching', but no explicit when-not-to-use or alternatives among siblings. Provides some guidance via return value mentioning 'recommended fetch strategy'.

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