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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that the tool has two operating modes, which is useful, but discloses nothing about pagination behavior, clamping, or result shape beyond what annotations and schema already convey.

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?

A single sentence with zero waste, front-loading the resource and the two-mode distinction. Nothing is padded or repeated.

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 read-only, flat query tool with a well-documented 6-parameter schema and no output schema requirement, the description plus schema gives an agent enough to invoke correctly. The one gap is absence of pagination or return-shape hints, which is minor here.

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 83%, so the schema already documents id, skip, sort, limit, and query with meaningful detail. The description reinforces the id/query dichotomy but adds no syntax, format, or edge-case guidance beyond the schema; baseline 3 applies.

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?

States a specific verb (Find) and resource (LimAdSenseSite records) and clearly splits behavior into two modes: single-record lookup by id versus filtered list via query. The resource name itself distinguishes it from the ~50 query_lim* siblings, but there is no explicit contrast drawn with any of 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 implies the selection rule between the two modes (pass id for one, query for a list), which is useful context. It does not state any when-not conditions, prerequisites, or alternatives, so usage is only implied rather than guided.

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