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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true. The description adds valuable behavioral context beyond those: it mentions the daily quota, the refusal tab when the model is not honest, and that it returns the sheet URL. It does not detail side effects like overwriting an existing sheet or permission requirements, but the quota and refusal-tab details are meaningful additions. No contradiction with 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?

Three sentences, each earning its place: the first states the action and output contents, the second states the return value, the third states the quota constraint. The most important information is front-loaded. No filler or repetition of schema details.

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 publish operation with no output schema, the description covers the key return value (sheet URL), the main side effect (quota consumption), and the content of the output. It does not mention whether the operation overwrites an existing sheet or how the refusal tab is triggered, but the annotations already signal destructiveness and open-world behavior. The description is reasonably complete for an agent to decide to call it.

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 the schema already documents both parameters ('id' and 'scenario'). The description adds context for 'scenario' by saying it is 'a server-run scenario as data tabs', which clarifies the purpose of the scenario parameter. However, it doesn't add format or syntax details beyond the schema. Baseline 3 is appropriate.

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 states a specific verb ('Publish'), a specific resource ('a stored model'), and a concrete destination ('the signed-in user's Google Sheets'). It also enumerates what gets published (model workbook, scenario data tabs, charts) and distinguishes itself from siblings like sim_publish_app and sim_publish_compare by naming the target and content. This is a clear, specific purpose statement.

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?

The description implies when to use this tool: when you need to publish a stored model to Google Sheets with live formulas, scenario data, and charts. It does not explicitly name alternatives or exclusions, but the sibling list includes sim_publish_app and sim_publish_compare, and the description's specificity about Google Sheets and the model workbook helps an agent infer the distinction. It lacks an explicit 'use X instead when...' statement, so it falls short of a 5.

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