ghl_brand_board_get_by_location

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

Annotations already declare readOnlyHint=true, idempotentHint=true. The description adds useful context: pagination parameters (limit, offset), OAuth scopes, and the endpoint path. No contradiction with 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?

The description is relatively concise, though it repeats 'Get Brand Boards' twice. The key information (retrieves all by location, pagination, auth) 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?

The description covers endpoint, pagination, and OAuth scopes. However, it does not mention the response format (likely a list), pagination behavior (e.g., next page tokens), or filtering options (search, deleted) which are present in the schema. Adequate but could be more 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%, so the description does not need to explain parameters. It mentions pagination (limit, offset) but not search or deleted. Baseline 3 is appropriate as the description adds minimal value beyond the schema.

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 states 'Retrieves all Brand Boards for a specific location', which is a specific verb (retrieves) and resource (brand boards) with a clear filter (by location). It distinguishes from sibling tools like create, delete, or get_by_id.

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 implies usage when you need brand boards for a location, but does not provide explicit when-to-use, when-not-to-use, or alternatives. No guidance on when to use this versus related tools like get_by_id.

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