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

Annotations already declare readOnly, idempotent and non-destructive, so the description's real contribution is the non-obvious pagination caveat: location_id is applied after BrightLocal returns a page, so pages can come back short while next_cursor continues. That is genuinely valuable behavior beyond the annotations, though rate limits or result ordering are not covered.

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?

Content is front-loaded: purpose first, then row shape, then constraints, then the sibling pointer. The column enumeration in the second sentence is dense but each item earns its place by telling the agent what it can rely on in the response. Slightly long but no filler.

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?

There is no output schema, and the description compensates by enumerating the returned fields, the pagination behavior, and the eligibility constraint that suppresses rows. An agent can call this correctly and interpret empty or short pages without further information.

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 both parameters are already documented; the description still adds real semantics by explaining that cursor is a continuation token from a prior call and that location_id filters post-retrieval per page rather than narrowing the server-side query. That goes beyond the one-line schema descriptions.

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 opens with a specific verb and resource ("List Local Search Grid reports") and enumerates the exact row contents (location, keywords, schedule, last run, status, grid size, points, average rank and change, re-run credits). It is clearly distinguished from the sibling get_local_search_grid_report, which is named as the tool for reading a single grid.

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?

It routes the agent explicitly to get_local_search_grid_report for reading an individual grid, and warns that locations without a Google Business Profile yield no rows. It does not spell out other conditions (e.g. use this to discover a report before fetching it), but the list-vs-read split is unambiguous.

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