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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. Beyond that, the description adds meaningful context: license holder names and names under review are never shown, an unknown slug returns {"error": "not_found"}, and the returned object is the JSON form of the page. It does not discuss auth or rate limits, but for a read-only public lookup that is minor.

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 purpose is front-loaded, but the first sentence is a long run-on inventory of every returned field (status, At a glance facts, why, photos, mentions, actions, sources) that a reader must parse to reach the actual instruction. Much of that enumeration earns its place given there is no output schema, yet it could be tightened considerably.

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?

With no output schema, the description carries the burden of describing return contents, and it does so thoroughly, including the error shape and the deliberate omissions around names. What it lacks is any statement of how this tool relates to the adjacent get_place/get_record tools for a one-param, high-complexity lookup surface.

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 baseline is 3, but the description adds value by naming the two slug families (listed place slug like tracks-tavern, record page slug like example-tavern-1a2b3c) and their provenance. That extra meaning helps the agent construct a valid argument rather than just reflecting the schema's example.

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 opening sentence gives a specific verb and resource ("Returns one business as its page shows it") and enumerates the merged data sources (listing, license records, entity data), which distinguishes it from a plain record or place fetch. It never names get_place or get_record as alternatives, so the differentiation from those siblings remains inferential rather than explicit.

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 does tell the agent which slugs are acceptable and where to obtain them (search_records or a /records/<slug> URL), which is real invocation guidance. However, it gives no when-to-use/when-not-to-use signal relative to get_place or get_record, leaving the agent to guess whether this tool supersedes them.

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