set_publish_settings

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

Describes side effects: mutates publish settings, changes discoverability and authentication requirements. States non-effects. No annotations provided, so description carries full burden. Lacks details on return values or potential failures, but sufficient.

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, front-loaded with purpose, side effects, exclusions, and requirements. No redundant information.

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 the tool complexity (4 params, 2 required, output schema exists), description covers purpose, side effects, non-effects, alternative, and auth requirement. Complete for selection and invocation.

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%, so baseline is 3. Description adds context about the role of parameters (template, auth) but does not provide additional semantic meaning 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?

Clearly states 'Update a Google Form's publishing and auth requirements.' Specific verb+resource, distinguishes from sibling batch_update_form which changes items.

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?

Explicitly states what it does and what it does not do, and provides an alternative: 'Does NOT change which items are on the form; for that use batch_update_form.' Also mentions required OAuth scope.

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