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

Annotations already state readOnlyHint=true and openWorldHint=true, so safety and world scope are covered. The description adds the useful caveat that violations are included only 'where published' and names the result fields, but it does not state ordering, limits, or failure behavior; those remain schema-only.

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?

One front-loaded sentence names the operation, the target, and the content returned. The parenthetical listing is efficient and there is no redundant prose.

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 lookup with rich schema descriptions and no output schema, the definition supplies enough to understand what is fetched and the publication caveat. It stops short of full completeness on when to use it versus alternatives and on pagination/order, though those are partly covered by the max_inspections schema description.

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%, including detailed restaurant_id and city descriptions, so the schema carries parameter semantics. The description adds only the 'one restaurant' scope and does not explain parameter formats or constraints 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 names a specific read operation (get inspection history) and resource (one restaurant), and lists the returned content (dates, scores/grades/results, violations). It is clear, but it does not explicitly contrast with sibling tools such as search_restaurants or rating_systems.

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 implies usage for a single restaurant that has already been identified, but gives no explicit when-to-use/when-not guidance or named alternative. The only routing hint is 'for one restaurant'; the dependency on search_restaurants appears only in the schema, not the description.

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