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

The annotations already establish that this is a read-only, closed-world lookup. The description adds valuable behavioral context by stating that the factsheet is owner-confirmed and warning that owner confirmation is not independent certification, which is important for interpreting trustworthiness.

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 two compact sentences with no wasted wording. The key qualifiers and caveat are front-loaded and easy to parse.

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 low-complexity read-only tool with one schema-documented parameter, the description covers the returned factsheet contents and an important certification caveat. Minor gaps remain around exact response structure and explicit sibling selection guidance, but the core information is present.

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 single slug parameter is already fully documented in the schema as coming from PressGEO. The description adds no additional detail about the parameter, making the baseline score appropriate.

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 clearly states that this tool returns a published, owner-confirmed factsheet for a local business and lists the fields it contains. It does not explicitly differentiate itself from siblings such as get_confirmed_entity, so the purpose is clear but sibling selection remains ambiguous.

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?

There is no explicit guidance on when to use this tool versus get_confirmed_entity or the list_* alternatives. The description implies retrieval of a factsheet by slug, but leaves the agent to infer the usage conditions.

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