ghl_brand_board_update

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

The description adds the HTTP method (PATCH) and OAuth scopes, which are beyond the annotations. However, it does not explicitly disclose that it performs a partial update or what the response contains. Annotations already indicate it is not read-only, not idempotent, and not destructive.

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 with three useful pieces of information: purpose, endpoint, and OAuth scopes. However, the first two sentences are redundant, and the structure could be improved by front-loading key 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?

The description lacks information about the response format (no output schema) and does not explain that the 'body' parameter can contain partial updates. Given the nested structure and no output schema, the description is insufficient for an agent to understand the full behavior.

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%, meaning all parameters have descriptions in the schema. The tool description adds no additional meaning for the parameters beyond what is already in the schema, so it meets the baseline but does not enhance understanding.

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 'Update a Brand Board' and 'Updates an existing Brand Board', using a specific verb and resource. It distinguishes from sibling tools like create, delete, and get by the verb, but does not explicitly differentiate from them.

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 context about the endpoint and required OAuth scopes, implying that a locationId and brand board ID are needed. However, it does not explicitly state when to use this tool over alternatives or provide scenarios for use.

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