ghl_custom_menu_get_by_id

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds endpoint details, OAuth scopes, security requirement, and response content. No contradictions. Provides behavioral context beyond the 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?

Description contains multiple pieces of info (auth warning, title, fetch description, endpoint, scopes) but some redundancy (title appears in both annotation and description). Could be more streamlined.

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 simple read tool with one parameter and no output schema, the description covers purpose, auth, endpoint, and response content. Lacks error handling details but is mostly complete.

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% for the single parameter 'customMenuId', which has a clear description. The description does not add extra parameter-specific details but includes the ID in the endpoint path. Baseline score of 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?

Description clearly states 'Get Custom Menu Link' and 'Fetches a single custom menus based on id'. It specifies the resource and action, and implies retrieval of a single configuration. However, it does not explicitly differentiate from sibling tools like list, but the verb 'Get' and 'single' make it 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?

Provides important auth context: requires agency-level token and OAuth scope. Does not explicitly state when to use this vs. other custom menu tools (e.g., list or update). Usage is implied but not formalized.

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