Dynamic Tables Suspend Dynamic Table

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds useful scope detail — that both automated refresh and lag evaluation stop — but says nothing about reversibility (resume), permission requirements, or billing/state effects.

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. It is efficient but arguably under-sized for a mutation tool, which is penalized under contextual completeness rather than here.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a state-changing operation the description omits prerequisites, confirmability of the suspended state, and the natural pairing with resume_dynamic_table.

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 100% and all three parameters (database, schema_name, table_name) are documented in the schema with quoting guidance. The description contributes no additional parameter meaning, so the baseline 3 applies.

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?

States a specific verb ('Suspend') and resource ('a dynamic table') plus what is being suspended (automated refresh and lag evaluation). An agent can distinguish it from dynamic_tables_resume_dynamic_table by name inference, but the description never names the counterpart explicitly.

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?

Usage is implied by the verb: suspend when you want to pause refresh and lag evaluation. There is no explicit guidance on prerequisites (table must be active), what happens to downstream consumers, or when to prefer refresh_dynamic_table or resume_dynamic_table instead.

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