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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description adds real information they do not: a per-call cost of 0.01 USDC on Base x402 and the X-Provider-Key header for customer-owned credentials. That is exactly the kind of payment/auth context an agent needs before calling a paid external API. It stops short of saying what happens on payment failure or on pages with no LocalBusiness markup.

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?

Two tight sentences, no filler, with the purpose front-loaded and the payment/auth constraints following. Slightly awkward that the payment information sits in the same breath as the purpose without a structural break, but nothing is wasted.

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 is the only source for the return shape, and "LocalBusiness structured data" does not say whether output is raw JSON-LD, normalized fields, or an error on missing markup. Cost and auth are well covered, which compensates partly for a one-parameter tool, but an agent still cannot predict the payload.

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% and the single url parameter is undocumented in the schema, so the description must carry the burden. It does not clarify whether the URL is the business's own page, a directory listing, or an endpoint expected to contain JSON-LD, nor what URL forms are accepted. The word "actual public" hints at live web fetching but adds little operational meaning.

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 gives a specific verb (parse), a specific resource (LocalBusiness structured data) and a scope qualifier (actual public), so an agent can tell it is an entity-schema extraction tool and not a general extractor like api_extract. It never names a sibling to differentiate from, and "parse" leaves slightly ambiguous whether the input is a page URL or a pre-fetched document.

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 statement of when to reach for this instead of the sibling extractors (api_extract, api_company_profile, api_healthcare_directory), no prerequisites, and no exclusions. The only implicit cue is that one URL parameter is required, which the schema already states.

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