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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and open-world retrieval are covered. The description adds useful behavioral context (claim previews, follow-up via get_claim, retain warnings, cite URLs), but does not cover pagination, rate limits, or auth needs. With annotations doing the safety work, this is adequate but not rich.

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?

Three sentences, front-loaded with the core purpose, then usage/provenance notes, then a conceptual clarification. No filler, though the entity-category sentence is slightly tangential to invocation.

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?

No output schema exists, and the description does explain the return shape at a high level (structured data plus claim previews). However, with 0% parameter schema coverage and a complex domain (multiple entity types, provenance linking), it leaves slug format, the condensed flag, and error/empty-result behavior undocumented.

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 0%, so the description must compensate for three parameters (slug, entity_type, condensed). It only implies entity_type via the category list and says nothing about slug format or the condensed flag. The gap is significant at 0% coverage.

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 (Retrieve) and resource (published entity profile with structured data and claim previews), which is clearer than the tautological title 'Get entity'. It also distinguishes scope by naming the entity categories (producers, beverages, people, restaurants). It doesn't explicitly contrast with sibling tools like get_producer or get_beverage, but the purpose is unambiguous.

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?

Gives clear operational context: follow returned claim_uid with get_claim for provenance, retain confirmation warnings, and cite real returned URLs. It also clarifies the conceptual boundary that profiled entities are independent businesses, not brands. No when-not-to-use exclusions are stated, so it falls short of a 5.

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