Workbooks List Workbook Embeds

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds no behavioral context of its own — no note on pagination, whether embedding must be enabled, or any authorization requirement for reading embed configs.

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 verb and resource land immediately. Its brevity is efficient, though it edges toward under-specification rather than genuine conciseness.

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 simple read tool with an output schema and annotations covering safety, the description is minimally viable. It omits any routing guidance relative to workbooks_create_workbook_embed, which is the main completeness gap given the large sibling set.

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% for the single workbook_id parameter, so the schema supplies no semantics. The description does not compensate by stating the expected identifier format (ID vs. name/path) or whether embeds are scoped to a workbook or an individual page.

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 (list) and resource (embed configurations) scoped to a workbook, which distinguishes it from the write-side sibling workbooks_create_workbook_embed. It does not, however, explicitly contrast itself with any sibling or note that it is scoped per workbook.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as workbooks_create_workbook_embed for creating embeds or workbooks_get_workbook for workbook-level metadata. The agent must infer the usage context entirely from the name.

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