ghl_custom_menu_update

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

Annotations indicate readOnlyHint=false and idempotentHint=true, consistent with an update operation. The description confirms it requires authentication and permissions but adds little beyond the annotations. No contradiction.

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?

The description is relatively concise and front-loads the critical security requirement. It includes endpoint and OAuth scopes, but could be slightly tighter without losing essential info.

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?

With no output schema, the description does not mention return values. The tool has many nested parameters, and while the description covers key usage constraints, it lacks completeness on behavioral details such as what the successful response contains.

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 coverage is 100%, and the description does not add parameter-specific details beyond what the schema provides. The agency-level token note is a useful context but not parameter semantics.

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 clearly states 'Updates an existing custom menu for a given company' with specific verb and resource. It does not explicitly differentiate from sibling tools like ghl_custom_menu_create or ghl_custom_menu_delete, but the name and context make the purpose clear.

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 provides a critical usage constraint: 'REQUIRES AN AGENCY-LEVEL (Company) TOKEN' and mentions OAuth scopes. However, it does not state when to use this tool versus alternatives like ghl_custom_menu_create or ghl_custom_menu_delete.

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