ghl_custom_menu_create

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

Annotations indicate non-read-only and non-destructive. Description adds security context (agency token, OAuth scopes, endpoint details) beyond annotations. However, it does not describe the response or side effects (e.g., what is returned on success).

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?

Description is relatively concise but includes redundant information (repeats title 'Create Custom Menu Link') and is slightly verbose with endpoint and OAuth details. Front-loads the critical token requirement. Could be tighter.

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 no output schema and a complex nested input, the description should at least hint at the return value (e.g., the created custom menu object). It does not do so. Missing this context limits completeness for an AI agent.

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?

Input schema has 100% description coverage, so the description is not required to explain parameters. It adds value by providing an external link for icon usage details, which supplements the icon parameter. Baseline 3, plus link → 4.

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?

Description clearly states 'Create Custom Menu Link' and 'Creates a new custom menu for a company,' using specific verb and resource. It distinguishes from sibling tools (delete, get, list, update) by being the create variant.

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 a critical security prerequisite: 'REQUIRES AN AGENCY-LEVEL (Company) TOKEN' and that operations are agency-access-only. Also mentions authentication and OAuth scopes. However, it does not compare to alternatives like update or delete.

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