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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description makes the destruction concrete ('full replacement, not a merge') and adds a concrete error contract (422 when canHaveFoodMenus is absent). It does not cover auth/permission requirements or rate limits, so it is strong but not exhaustive.

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 dense sentences, each earning its place: replacement semantics first, then structure, then the prerequisite/error condition. No filler and the critical constraint is front-loaded.

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 3-parameter mutation tool with full annotation coverage and no output schema, the description covers the destructive semantics, the nested data shape, and the failure mode. Nothing essential for calling it correctly is missing.

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 baseline is 3, but the description adds meaning by explaining the menu -> sections -> items nesting and the required languageCode/currencyCode/units fields that the agent must populate inside the free-form menus array. This is genuinely useful beyond the schema's terse example.

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 (replace) and resource (food menus on a Google Business Profile location), and the word 'Replace' plus 'Full replacement, not a merge' immediately distinguishes it from the sibling google_business_food_menus_get. An agent can tell what it does without opening the schema.

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?

Gives clear context and a real precondition: the location must have metadata.canHaveFoodMenus or the call returns 422, and the operation is a full replacement rather than a merge. However, it never explicitly names google_business_food_menus_get as the read alternative or spells out when to prefer one over the other, so routing is left partly to inference.

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